Posts by nedmanjo

1) Message boards : Number crunching : Optimizing the apps (Message 1152)
Posted 8 days ago by Profile nedmanjo
Post:
Good question. I ran up one (1) WU per GPU at stock and OC and then two (2) WU's per GPU at stock and OC. My results favor two (2) WU's per GPU.

With stock settings, just one (1) WU per GPU, I posted 437.39 (7.3 min.) and 444.68 (7.4 min.) per task.
Reverting back, same settings but two (2) WU's per GPU, I posted ~ 814.8 (13.6 min.) or 6.8 min. per task and 821.9 (13.7 min.) or 6.85 min per task.

With slight OC, just one (1) WU per GPU, I posted 357.43 (6 min.) and 404.16 (6.7 min.) per task.
Reverting back, same settings but two (2) WU's per GPU, I posted ~ 702.6 (11.7 min.) or 5.85 min. per task and 752.9 (12.5 min.) or 6.3 min per task.

verbose=1
kernels_per_reduction=48
threads=8
lut_size=17
sieve_size=30
cache_sieve=1
sleep=1
2) Message boards : Number crunching : Optimizing the apps (Message 1151)
Posted 8 days ago by Profile nedmanjo
Post:
I'm running some single GPU WU's now. Initial WU's are at ~ 7.5. If I set at threads=9 I produce "Error while computing" WU's.

verbose=1
kernels_per_reduction=48
threads=8
lut_size=17
sieve_size=30
cache_sieve=1
sleep=1
3) Message boards : Number crunching : Optimizing the apps (Message 1149)
Posted 8 days ago by Profile nedmanjo
Post:
Swapped out my two GPU's, again. Sold the two EVGA GTX 1070 SC ACX's for two Nvidia GTX 1080 Founders Edition. Using the recommended settings I was getting "Error while computing" but then reduced threads and sieve_size down a point and am getting stable operation and valid results.

verbose=1
kernels_per_reduction=48
threads=8
lut_size=17
sieve_size=29
cache_sieve=1
sleep=1

Still running two WU's per GPU, measures faster than 1 WU per GPU. Utilization is at a steady 100% as currently configured.

<app_config>
<app>
<name>period_search</name>
<max_concurrent>4</max_concurrent>
<gpu_versions>
<gpu_usage>0.50</gpu_usage>
<cpu_usage>0.25</cpu_usage>
</gpu_versions>
</app>
<app>
<name>collatz_sieve</name>
<max_concurrent>4</max_concurrent>
<gpu_versions>
<gpu_usage>0.50</gpu_usage>
<cpu_usage>0.25</cpu_usage>
</gpu_versions>
</app>
</app_config>

If anyone has suggestions for further improvement please do tell.
4) Message boards : Number crunching : Optimizing the apps (Message 1047)
Posted 18 Sep 2018 by Profile nedmanjo
Post:
Woot! Hit > 900M Collatz credits today!!! And hit > 1,000M total credits in BOINC!!! Picked up a couple of used EVGA 1070 SC ACX's, yup, sold the Vega. These 1070's are humming along at a combined > 10M credits per day! Shooting for > 1,000M on Collatz! Power consumption is no more than the Vega plus 4M more credits per day. The posted configuration data is priceless. Thanks to all.

verbose=1
kernels_per_reduction=48
threads=9
lut_size=17
sieve_size=30
cache_sieve=1
sleep=1

<app_config>
<app>
<name>period_search</name>
<max_concurrent>4</max_concurrent>
<gpu_versions>
<gpu_usage>0.50</gpu_usage>
<cpu_usage>0.25</cpu_usage>
</gpu_versions>
</app>
<app>
<name>collatz_sieve</name>
<max_concurrent>4</max_concurrent>
<gpu_versions>
<gpu_usage>0.50</gpu_usage>
<cpu_usage>0.25</cpu_usage>
</gpu_versions>
</app>
</app_config>
5) Message boards : Number crunching : Optimizing the apps (Message 1032)
Posted 14 Sep 2018 by Profile nedmanjo
Post:
Configuration file locations (on Windows, replace the first path components on other OSs accordingly):

C:\ProgramData\BOINC\projects\boinc.thesonntags.com_collatz\<app_name>.config

During project initialization on your client, empty <app_name>.config files will be created for each of the application versions that match your GPUs. You can enter parameters into these files in order to deviate from default values, and they will be picked up as soon as a Collatz GPU task starts.

Configuration file format

Plain text file, one "parameter=value" pair per line, unrecognized parameter names are simply ignored (you can use this to comment out some parameters during testing), missing parameters fall back to their default values.

Example (suitable for a GTX 1080):
kernels_per_reduction=48
threads=9
lut_size=17
sieve_size=30
cache_sieve=1

Parameters

cache_sieve
default: 1 (?)
range: 0 or 1 (?)
definition: "any setting other than 1 will add several seconds to the run time as it will re-create the sieve for each WU run rather than re-using it"

kernels_per_reduction
default: 32
range: 1...64
definition: "the number of kernels that will be run before doing a reduction. Too high a number may cause a video driver crash or poor video response. Too low a number will slow down processing. Suggested values are between 8 and 48 depending upon the speed of the GPU."
comment: "affects GPU usage and video lag the most from what I [sosiris] tested."

lut_size
default: 10
range: 2...31
definition: "the size (in power of 2) of the lookup table. Chances are that any value over 20 will cause the GPU driver to crash and processing to hang. The default results in 2^10 or 1024 items. Each item uses 8 bytes. So 10 would result in 2^10 * 8 bytes or 8192 bytes. Larger is better so long as it will fit in the GPUs L1/L2 cache. Once it exceeds the cache size, it will actually take longer to complete a WU since it has to read from slower global memory rather than high speed cached memory."
comment: "I [sosiris] choose 16, 65536 items for the look up table because it would fit into the L2$ (512KB) in GCN devices. IMHO it could be 20 for NV GPUs, just like previous apps, because NV GPUs have better caching."

reduce_cpu
default: 0
range: 0 or 1
definition: "The default is 0 which will do the total steps summation and high steps comparison on the GPU. Setting to 1 will result in more CPU utilization but may make the video more responsive. I have yet to find a reason to do the reduction on the CPU other than for testing the output of new versions."
comment: "I [sosiris] choose to do the reduction on the CPU because AMD OpenCL apps will take up a CPU core no matter what you do (aka 'busy waiting') and because I want better video response."

sieve_size
default: ?
range: 15...32
definition: "controls both the size of the sieve used 2^15 thru 2^32 as well as the items per kernel are they are directly associated with the sieve size. A sieve size of 26 uses approx 1 million items per kernel. Each value higher roughly doubles the amount. Each value lower decreases the amount by about half. Too high a value will crash the video driver."

sleep
default: 1
range: ?
definition: "the number of milliseconds to sleep while waiting for a kernel to complete. A higher value may result in less CPU utilization and improve video response, but it also may lengthen the processing time."

threads
default: 6
range: 6...11
definition: "the 2^N size of the local size (a.k.a. work group size or threads). Too high a value results in more threads but that means more registers being used. If too many registers are used, it will use slower non-register memory. The goal is to use as many as possible, but not so many that processing slows down. AMD GPUs tend to work best with a value of 6 or 7 even though they can support values of up to 10 or 11. nVidia GPUs seem to work as well with higher values as lower values."
comment: "I [sosiris] didn't see lots of difference once items per work-group is more than wavefront size (64) of my HD7850 in the profiler."

verbose
default: 0
range: 0 or 1
definition: "1 will result in more detail in the output."

Definitions are taken from Slicker's post from June 2015, last modified in September 2015.
Comments are taken from sosiris' post from June 2015.
Edit April 28 2018, added definition of cache_sieve from a post from Slicker from April 2018
6) Message boards : Number crunching : Optimizing the apps (Message 940)
Posted 25 Aug 2018 by Profile nedmanjo
Post:
Smokin' fast! Nice!
7) Message boards : Number crunching : Optimizing the apps (Message 935)
Posted 22 Aug 2018 by Profile nedmanjo
Post:
Back up and running. Vega Frontier failed, took my MB out with it. The good, RMA replacement GPU, thank you AMD, the bad, new MB. So far, so good. No thermal issues or issues otherwise.
8) Message boards : Number crunching : Optimizing the apps (Message 806)
Posted 19 Jul 2018 by Profile nedmanjo
Post:
I take it this is the CPU config file? "collatz_sieve_1.40_windows_x86_64" Are there any optimizations for this like for the "collatz_sieve_1.30_windows_x86_64__opencl_nvidia_gpu" config file?
9) Message boards : Number crunching : Optimizing the apps (Message 642)
Posted 6 Jul 2018 by Profile nedmanjo
Post:
Hi Martin, Appreciate your advice. I may get to that in time. Prior to Flashing the BIOS I found an error, SMBIOS 0X01 P1-DIMMB1 Single Bit ECC Memory Error. Could be the error originated from the multiple system crashes, could be I have a bad memory module. Happens. I'm creating a Memtest86 bootable USB drive to check it out.

Regarding the GPU. It simply won't run any GPU tasks (Collatz, GPUGrid, Amicable...) with any of the three AMD drivers written specific for this card. Not at default settings, not tweaked. Runs just several minutes, screen corrupts, goes black and there's no getting it back. I had no such issues for the first week. Ran stable 24/7 at default settings but throttled constantly. Downclocking eliminated the throttling and it was stable at ~ 1400Mhz at 20 degrees below its thermal ceiling. Ran great for several days. I had my best day ever at 6,610,612 credits!

Something changed... bad hardware, software, settings... don't know.

So, reseated the hardware, no issues found. Flashed the BIOS so it's factory configured with minor but necessary adjustments. I'll run a full test of the memory modules and we'll see where we go from there.

Thanks, I appreciate you reaching out.
10) Message boards : Number crunching : Optimizing the apps (Message 635)
Posted 5 Jul 2018 by Profile nedmanjo
Post:
Update.... I have no clue... no stablity with GPU under load at stock settings or otherwise. So, start from scratch.

Flash BIOS
Restore Defaults
Reseat hardware
Reinstall OS & Drivers
Test
Upon Fail... stick cattle prod in box, then activate.

much apologies for all the lost WU's.

:(
11) Message boards : Number crunching : Optimizing the apps (Message 599)
Posted 4 Jul 2018 by Profile nedmanjo
Post:
Problem sorted but not fully understood. It was tied to running LHC but not at 75% as I assumed, I was running 23 WU's at 100%. So much for going off memory. MB thermals were fine but guess this PC couldn't take it. Reduced the CPU use % to 75% and I'm stable again. It's not the first time I've run CPU projects at 100%, some projects don't drive high thermals and when they do I reduce % use. Lesson learned.
12) Message boards : Number crunching : Optimizing the apps (Message 598)
Posted 4 Jul 2018 by Profile nedmanjo
Post:
The Vega FE gaming driver was rock solid until yesterday. Thermals were good, steady clock, no apparent points of concern. Then, suddenly, my PC locked up. Have been working to get it settled since. Evidently a finicky card and or drivers. Had to do a clean uninstall, reboot, then install the Radeon Pro Enterprise driver 18.Q2.1, reboot, then install the Radeon Adrenalin driver 18.4.1, reboot. Same issue returned. I gave the Crimson Blockchain driver a go and it ran well, for a while, and without tweaking but then the PC locked up again.

So, at the moment, I'm a bit perplexed. The only thing I changed leading up to this was my CPU based project. Thought I'd run LHC. Long CPU intensive work but shouldn't be related. I'm running two E5-2667's v2 and only using 75% of the cores at 75%.

I'll see how it does just running Collatz and WUProp. See if the stability returns.
13) Message boards : Number crunching : Optimizing the apps (Message 571)
Posted 28 Jun 2018 by Profile nedmanjo
Post:
I think I'd need to be at < 350 seconds per single WU to achieve two WU's at 700 seconds each. Running with current settings. Looks steady, thermals are good. We'll see how it does. I've currently got the core steady at ~ 1,400Mhz with good thermals. Specs indicate it should be able to run steady > 1,400Mhz but I'm thinking it will definitely take some time and effort to settle the thermals and steady the core.

Update: > 900 seconds each, pushed the core clock and voltage and for my efforts got a back screen and a frozen GUI. The best part was to come when I rebooted.... more black screen... not a process for the weak of heart.

14) Message boards : Number crunching : Optimizing the apps (Message 568)
Posted 27 Jun 2018 by Profile nedmanjo
Post:
Yes, much improved and much improved performance vs the two Titan Black's I retired. Loved those cards but they were making my electric meter whirl and I'm no longer in danger of passing out from heat exhaustion. Both of my Titans ran near their thermal limit... was so hot. The Vega FE is running 20 degrees cooler and it's one thermal plant vs two. Did some more tweaking this morning, ran below 400 seconds per WU all day!
15) Message boards : Number crunching : Optimizing the apps (Message 564)
Posted 27 Jun 2018 by Profile nedmanjo
Post:
Switched to Vega Gaming Driver so I could use OnedriveNTool to Down volt the card. I read that could address the throttling problem. So, down volted the card and I'm now under 450 seconds per WU. Less power, dropped the GPU temp by 5. Nice! Probably no where near optimized but improved. GPU clock is stable just under 1,200Mhz.
16) Message boards : Number crunching : Optimizing the apps (Message 563)
Posted 26 Jun 2018 by Profile nedmanjo
Post:
I've increased, decreased various parameters. Can't seem to reduce the time further. My GPU does seem to throttle.

Spec's say GPU Clock speed: 1382MHz “typical,” 1600MHz peak

- GPU Clock cycling between 1100MHz - 1200MHz
- Memory clock cycling between 500 - 945MHz
- Temperature cycling within a few degrees of limit
17) Message boards : Number crunching : Optimizing the apps (Message 562)
Posted 26 Jun 2018 by Profile nedmanjo
Post:
Currently running one task. ~ 600 +/- 5 seconds per. Current settings:

verbose=1
kernels_per_reduction=48
threads=8
lut_size=17
sieve_size=30
cache_sieve=1
sleep=1
reduce_cpu=0
18) Message boards : Number crunching : Optimizing the apps (Message 552)
Posted 26 Jun 2018 by Profile nedmanjo
Post:
Trying to optimize an AMD Vega Frontier.

verbose=1
kernels_per_reduction=48
threads=7
lut_size=16
sieve_size=30
cache_sieve=1
sleep=1
reduce_cpu=0

Running two tasks simultaneously, finishing between 1,000 - 1,100 seconds each. GPU utilization is at 99 - 100%, some signs of throttling.

Tasks at 6 or 8 threads seem slower, at 9 they abort. lut_size at 17 seems to cause a pause every few cycles.

Any benefit to adding kernels_per_reduction?

Any help / guidance would be appreciated.
19) Message boards : News : Use at your own risk (Message 332)
Posted 13 May 2018 by Profile nedmanjo
Post:
Having same issue as others have reported. No WU's are dropping. Been using the same NVidia driver v391.24, not the recently reported version that had an issue v397.31. For GP's performed a reset, no change, and detached, reattached the project, again no change. GPUGrid has been running since without issue.
20) Message boards : Number crunching : Dual GPU question (Message 93)
Posted 21 Apr 2018 by Profile nedmanjo
Post:
GPU portion is same as what's in my cc_config file I'm running two Titan Blacks, 2 tasks per GPU.

<cc_config>
<options>
<use_all_gpus>1</use_all_gpus>
<report_results_immediately>1</report_results_immediately>
</options>
</cc_config>

Did you check your app-config file?

<app_config>
<app>
<name>collatz_sieve</name>
<max_concurrent>4</max_concurrent>
<gpu_versions>
<gpu_usage>0.50</gpu_usage>
<cpu_usage>0.50</cpu_usage>
</gpu_versions>
</app>
</app_config>


Next 20


©2018 Jon Sonntag; All rights reserved