Posts by Harri Liljeroos

1) Message boards : Number crunching : How to optimize GPU configuration? (Message 1832733)
Posted 7 days ago by Harri Liljeroos
The CPU % limit applies to CPU tasks only. It has no effect on GPU tasks.

By default the NV SOG application needs a full CPU core per each task. I that is a problem to you use the -use_sleep command line parameter, this will lower the CPU usage for that application. Read the "ReadMe_MultiBeam_OpenCL_NV_SoG.txt" in docs folder under projects/setiathome.berkeley.edu. There is decribed a lot more about the command line parameters that can be used. Also you can read the Raistmer's sticky thread http://setiathome.berkeley.edu/forum_thread.php?id=80381 about 8.19 Windows GPU application support thread.
2) Message boards : Number crunching : Looking for a program to deal with drive usage.... (Message 1832160)
Posted 10 days ago by Harri Liljeroos
Is it this one http://hdgraph.com/?
3) Message boards : Number crunching : Spammers (Message 1830728)
Posted 19 days ago by Harri Liljeroos
Wouldn't it be easier to limit the length of username that is visible in the forum pages? I mean to show only maybe 25 characters or something.
4) Message boards : Number crunching : Tracking in Windows 7 (Message 1830276)
Posted 21 days ago by Harri Liljeroos
I cannot find a service with that exact name although I installed that Quality rollup. I can find the following services: 'Diagnostic policy Service' (Running), 'Diagnostic Service Host' (Running), 'Diagnostic System Host' (Stopped), 'Diagnostic Tracking Service' (Running) and 'Distributed Link Tracking Service' (Running). I don't know if any of those is a result of the Quality rollup update or not.
5) Message boards : Number crunching : The wonders of Micro$oft Windoze (Message 1830152)
Posted 21 days ago by Harri Liljeroos
^ That could also do the trick. I tried killing the wuaueng.dll thread (which is consuming all the cpu time) inside svchost.exe using Sysinternals Process Explorer as an administrator but that didn't let the manual update installation proceed.
6) Message boards : Number crunching : The wonders of Micro$oft Windoze (Message 1830055)
Posted 22 days ago by Harri Liljeroos
I have just been having the exact same problem. Windows 7 checking for the updates takes forever (nothing in 12 hours) and one instance of svchost.exe taking a full CPU constantly. Running the Troubleshooting from Control Panel as suggested didn't result to anything as it gets stuck in the same situtation when it is checking for the updates on the net.

Then I tried the Cosmic_Ocean's suggestion of KB3102810 but no help. I had this already installed but uninstalling and reinstalling it didn't change help.

But then I found this http://www.ghacks.net/2016/11/02/checking-for-updates-slow-on-windows-7-here-is-the-fix/ and I installed the July 2016 update rollup which fixed my problem.

The manual installation of Microsoft updates was also stuck when it checks the updates available on my computer. The trick was to reboot the computer and immediately on restart manually install the update before normal windows update was started (before the svchost.exe hogs the CPU).
7) Message boards : Number crunching : Open Beta test: SoG for NVidia, Lunatics v0.45 - Beta6 (RC again) (Message 1823772)
Posted 12 Oct 2016 by Harri Liljeroos
Firefox, Chrome and IE are all trying to block this download. IE allowed me to bypass the warnings and download it anyway. When scanned wit Avast no problems were found.

After I installed this it didn't restart Boinc but I started it manually. All are running normally now but I was already running these applications (SoG r3528 as 8.12) so that's no surprise.
8) Message boards : Number crunching : BOINC does not identify GPUs correctly (Message 1816606)
Posted 12 Sep 2016 by Harri Liljeroos
I won't worry. I just have to remember it for future reference. :)
9) Message boards : Number crunching : BOINC does not identify GPUs correctly (Message 1816604)
Posted 12 Sep 2016 by Harri Liljeroos
I have similar situation. My GPUs are factory overclocked. The newer GTX970 has a bit higher clock than the older and Boinc sees the faster as GPU0.
10) Message boards : Number crunching : BOINC does not identify GPUs correctly (Message 1816339)
Posted 11 Sep 2016 by Harri Liljeroos
I am not using the latest driver but version 361.91 (same as when GTX650 Ti was in use). I reinstalled it though after changing the GPU. Anyway it is good to know if you have to debug a system that what Boinc shows you may not be the whole truth.
11) Message boards : Number crunching : BOINC does not identify GPUs correctly (Message 1816178)
Posted 10 Sep 2016 by Harri Liljeroos
Boinc identifies GPU0 and GPU1 incorrectly.

Here's the story what I see: I used to have on one of my hosts two Nvidia GPUs a GTX970 (GPU0) and a GTX650 Ti (GPU1). Boinc, GPU-Z and Nvidia Inspector agreed which one was GPU0 and which GPU1. Then this week I bought a new GTX970 which is identical to the old GTX970 (Asus Strix-GTX970-DC2OC-4GD5) and replaced the GTX 650 Ti with the new GTX970. Now Boinc disagrees with GPU-Z and Nvidia Inspector about which one is GPU0 and which is GPU1.

Below is a link to a picture of a situation when one GPU is starting a new task. Boinc shows that GPU1 (d1) is starting the new task but Nvidia Inspector shows that it is GPU0 which has the load at 0%.

Does anybody else see similar situation on a host that has two identical GPUs?

https://1drv.ms/i/s!AsrPYtj_-FTpgZRD_5gO3nNmY_e3dQ
12) Message boards : Number crunching : SETI applications for NVIDIA GPU improvement - how you can help (Message 1805930)
Posted 30 Jul 2016 by Harri Liljeroos
New set of builds (r3500) available here: https://cloud.mail.ru/public/LJ8s/c3WyRR8ip
Please test


I don't see much difference to the previous version. Slightly more lags but not too bad. When running with defaults same situation. When I freed two CPU cores and tried with a minimal commandline:
-sbs 1024 -hp -instances_per_device 1 -cpu_lock

I got a driver restart. Here's the WU where it happened: http://setiathome.berkeley.edu/result.php?resultid=5065787291
13) Message boards : Number crunching : SETI applications for NVIDIA GPU improvement - how you can help (Message 1805568)
Posted 29 Jul 2016 by Harri Liljeroos
The test with freeing a CPU core for feeding the GPUs resulted the already known conclusion: one free CPU core is not enough for two GPUs to maximize the GPU load. For best result you should free one CPU core for each GPU (while running one WU/GPU at a time). This is for my host, but YMMV. Now I'm back to using my old app_config and commnadline parameters.


I would recommend to try also -hp -cpu_lock addition to your tuning line to improve GPU load with busy CPU.


The -hp was there already but I'm adding the -cpu_lock now. So new commandline is:
-sbs 1024 -use_sleep -hp -period_iterations_num 5 -instances_per_device 1 -spike_fft_thresh 4096 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 32 -oclfft_tune_cw 32 -tt 75 -cpu_lock


The -sbs 1024 applies to GTX970 only as the application seems to limit that value to 25% of GPU's memory. So GTX 650Ti only uses -sbs 256.
14) Message boards : Number crunching : SETI applications for NVIDIA GPU improvement - how you can help (Message 1805554)
Posted 29 Jul 2016 by Harri Liljeroos
The test with freeing a CPU core for feeding the GPUs resulted the already known conclusion: one free CPU core is not enough for two GPUs to maximize the GPU load. For best result you should free one CPU core for each GPU (while running one WU/GPU at a time). This is for my host, but YMMV. Now I'm back to using my old app_config and commnadline parameters.
15) Message boards : Number crunching : SETI applications for NVIDIA GPU improvement - how you can help (Message 1805323)
Posted 28 Jul 2016 by Harri Liljeroos
And what about running with defaults?

Today I have started running with default settings, so no commandline and lately also without app_config. I am positively surprised how well the host is behaving. The load on GPUs is of course fluctuating as there are no free CPU cores to feed them constantly but I have no big lags or driver restarts. On CPU there is running 6 setiathome_v8 tasks and 2 CPDN wah2_eu25 tasks so CPU load is constantly at 100%.

I can also use the computer for email, surfing the net and I could view the new Seti video from Youtube without a problem (Firefox HW-acceleration is turned off).

I am using the r3486 release with date 19.7.2016 on the exe.

Here are a few WUs I have crunched so far with default settings:
http://setiathome.berkeley.edu/result.php?resultid=5063178279 a Guppi VLAR on GTX970.
http://setiathome.berkeley.edu/result.php?resultid=5063162557 normal Arecibo WU on GTX970.
http://setiathome.berkeley.edu/result.php?resultid=5063120898 normal Arecibo WU on GTX650Ti.
http://setiathome.berkeley.edu/result.php?resultid=5063178278 a Guppi VLAR on GTX650Ti.

So good job Raistmer on this application.

(edit)Next I try and free one CPU core and see what that does.(/edit)
16) Message boards : Number crunching : SETI applications for NVIDIA GPU improvement - how you can help (Message 1805206)
Posted 27 Jul 2016 by Harri Liljeroos
Well my experience without the -use_sleep parameter was a driver restart within 5 minutes of starting the application. So I was forced to go back to -use_sleep. The application does use a lot less CPU compared to previous versions. I am currently running with -period_iterations_num 5 with no lag on this host: http://setiathome.berkeley.edu/results.php?hostid=7043787, decreasing it to 3 and lags will appear. The host has two GPUs: a GTX650Ti and a GTX970 both running one seti task at a time with three CPU cores reserved for GPU feeding. The host's GPUs do also Einstein WUs one or two at a time depending on how BOINC is scheduling them (seti share is 45 and einstein is 25).
17) Message boards : Number crunching : SETI applications for NVIDIA GPU improvement - how you can help (Message 1802989)
Posted 16 Jul 2016 by Harri Liljeroos
Please test this build: https://cloud.mail.ru/public/9ifo/XQTdqmfJJ
Look for CPU usage vs r3486.


http://setiathome.berkeley.edu/result.php?resultid=5042270028 Here's one that was crunched with this version. Stderr misses the normal output of used parameters but includes a lot of other other information. The CPU use don't seem to be any different to the previous r3486 version. The parameters used were:
-sbs 384 -use_sleep -hp -instances_per_device 1 -spike_fft_thresh 4096 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 32 -oclfft_tune_cw 32


It was run on my GTX970.

In general all these SoG applications are very sensitive to the CPU load. If it reaches 100% the driver reset is bound to happen although I have now the TdrDelay set at 8 seconds. So I have reserved 1.6 CPU cores per MB task because this is also my daily driver so extra head room is required. I will set up now the non-Boinc use limit to 18% to ease the effect of other running applications.
18) Message boards : Number crunching : SETI@home v8.12 Windows GPU applications support thread (Message 1799316)
Posted 29 Jun 2016 by Harri Liljeroos
There is new set of RC builds available here: https://cloud.mail.ru/public/8RM1/LMYTwvGYp
If you experience any issues with v8.12 please try new RC build instead.


Here's a WU done with the new app. http://setiathome.berkeley.edu/result.php?resultid=5010274940

The output on this task looks a lot different than before, can't even see which GPU was used. I see quite a lot of these.

On the other hand here's another task that the output looks normal: http://setiathome.berkeley.edu/result.php?resultid=5010142578
19) Message boards : Number crunching : SETI@home v8.12 Windows GPU applications support thread (Message 1798223)
Posted 23 Jun 2016 by Harri Liljeroos
Harri wrote:
I will reduce the -period_iterations_num value until the driver restarts stop.

Double-check that.

Raistmer wrote:
Param should be increased not reduced. Default is 50. Task you list has 30. It can be the reason of driver restart. Try to set it let say to 100.


Ah a logical typo, of course I ment increase. So far with value 35 I've had no restarts.

I'm off to celebrate mid-summer so next comments from me on sunday or monday. I'll leave the computer crunching.
20) Message boards : Number crunching : SETI@home v8.12 Windows GPU applications support thread (Message 1798189)
Posted 23 Jun 2016 by Harri Liljeroos
That's the plan. I will reduce the -period_iterations_num value until the driver restarts stop.

For the TDR registry, should I specify only the TdrDelay value or should I create all of those mentioned on the Microsoft page you linked? Currently I cannot find any of those in my registry.


Next 20


 
©2016 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.