Try Brent's idea first.

If it doesn't correct then I'll resubmit my question

I have the cmdline set for: -use_sleep -instance_per_device 3
I've also had the cmdline set for 2 also, makes no difference.

Changing the -instance per device from 3 to 2, exiting & restarting BOINC, and the manager still shows 0.04C + 0.33NV in the Use column?
If that is the case, it indicates it is using some other settings, from somewhere else.

Do you have a app_config.xml file in the C:\ProgramData\BOINC\projects\setiathome.berkeley.edu
folder?


EDIT- which application are you presently using? These settings are for when running SoG.

---

Grant
Darwin NT

Of the three wu's I'm working on 2 are having trouble(I'm trying 0.45 again with 0.5/0.1 as suggested), the time left does not shrink at all, processing slows to a crawl, when I stop boinc, all 4 of the cpu wu's and 1 of 3 gpu's stop, the other 2 gpu wu's stay in Memory and continue, plus the cpu% keep dropping.

Might be an idea to start again.
Set BOINC not to start at login/bootup.
Exit BOINC.
Re-boot.

Once re-booted, use Task Manager to check that BOINC (and the applications) are no longer running.

Re-run the 0.45 installer- select SoG or CUDA50.

Check how many GPU WUs are being processed, without an app_config.xml it should just be one per GPU.
The GPU WU will most likely be high priority, and when they start the 2 that have the over long completion times will also be High Priority.
Once they are done, everything should then settle back down again and you can re-enable BOINC to start with the system/logon again.


If you want to run multiple WUs on the GPU i'd suggest using app_config.xml to do so as all you have to do is "Select options, Read config files" (on the manager) for the settings to take effect.
And they don't get wiped when you re-run the installer.


1 WU, no CPU cores reserved (the default).

<app_config>
 <app>
  <name>setiathome_v8</name>
  <gpu_versions>
  <gpu_usage>1.00</gpu_usage>
  <cpu_usage>0.04</cpu_usage>
  </gpu_versions>
 </app>
</app_config>

2 WUs, 2 CPU cores reserved.

<app_config>
 <app>
  <name>setiathome_v8</name>
  <gpu_versions>
  <gpu_usage>0.50</gpu_usage>
  <cpu_usage>1.00</cpu_usage>
  </gpu_versions>
 </app>
</app_config>

3 WUs, 3 CPU cores reserved

<app_config>
 <app>
  <name>setiathome_v8</name>
  <gpu_versions>
  <gpu_usage>0.33</gpu_usage>
  <cpu_usage>1.00</cpu_usage>
  </gpu_versions>
 </app>
</app_config>

---

Grant
Darwin NT

Set your cache to 1 day and just let it run.

You have changed apps so much BOINC has no idea what the average times should be.

It will run high priority until it sorts it out.

I had set it at 1 day, 0.45 ran only cpu wu's all night...
So much so that I just went back to cuda processing...

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I have the cmdline set for: -use_sleep -instance_per_device 3
I've also had the cmdline set for 2 also, makes no difference.

Changing the -instance per device from 3 to 2, exiting & restarting BOINC, and the manager still shows 0.04C + 0.33NV in the Use column?
If that is the case, it indicates it is using some other settings, from somewhere else.

Do you have a app_config.xml file in the C:\ProgramData\BOINC\projects\setiathome.berkeley.edu
folder?


EDIT- which application are you presently using? These settings are for when running SoG.

Yes, I have always had an app info file, SoG isn't working, 0.01% work done all night on the gpu, even on the High Priority stuff. SoG and My 580 aren't getting along... So I went back to what works.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I am using the low perfGPU version.Just one task on the GPU.
A number of times it just stops: boinc task appears to be running,elapsed time is increasing, but GPU load zero and no cpu usage either.
When shutting down boinc completely,the gpu process keeps running, well, it is not shut down. I have to kill it manually.
I am still in the process to increase the -period_iterations_num to a point, where every tasks finishes.

As the title says. Beta test only, try at your own risk.

I think we should dig out the old "Advanced Users only" tag for this one - I'm not sure whether it will fly or not.

This installer has been updated for NVidia only so far - DO NOT USE IT if you are currently running stock applications for ATI/AMD or intel GPUs.

This is basically the v0.44 installer (64-bit only, to start with), with the following changes....

Beta2 now available, in both 64-bit and 32-bit versions. Pick the right one, or test out my new dialogs...

Now includes new r3430 ATI and intel_gpu versions, with extra app_version entries to correspond with the new stock applications deployed on 19 May.

ReadMes not yet updated: we polish those up last, to take account of feedback received from testers.

Now updated again with Beta3 (both 64-bit and 32-bit).

Only change is to incorporate r3472 of the SoG application - see release notes in the SETI@home v8.12 Windows GPU applications support thread (and please post comments on the SoG application there, not here).

I have to drive across to the other side of the country tomorrow morning, so I'll leave Beta2 in place until people report successful downloads and installations. Please check carefully that you download the version you wanted to test. (I'm getting error messages myself when I try to download just now)

Download url is: https://onedrive.live.com/redir?resid=8D83BF774A4A86F5!979&authkey=!AK7t-36P9nAec2Y&ithint=folder%2cexe

Now updated again with Beta3 (both 64-bit and 32-bit).

Only change is to incorporate r3472 of the SoG application - see release notes in the SETI@home v8.12 Windows GPU applications support thread (and please post comments on the SoG application there, not here).

I have to drive across to the other side of the country tomorrow morning, so I'll leave Beta2 in place until people report successful downloads and installations. Please check carefully that you download the version you wanted to test. (I'm getting error messages myself when I try to download just now)

Download url is: https://onedrive.live.com/redir?resid=8D83BF774A4A86F5!979&authkey=!AK7t-36P9nAec2Y&ithint=folder%2cexe

. . FWIIW I just downloaded Beta3 AOK, will try from the other machine and test the install on that rig.

Now updated again with Beta3 (both 64-bit and 32-bit).

Only change is to incorporate r3472 of the SoG application - see release notes in the SETI@home v8.12 Windows GPU applications support thread (and please post comments on the SoG application there, not here).

I have to drive across to the other side of the country tomorrow morning, so I'll leave Beta2 in place until people report successful downloads and installations. Please check carefully that you download the version you wanted to test. (I'm getting error messages myself when I try to download just now)

Download url is: https://onedrive.live.com/redir?resid=8D83BF774A4A86F5!979&authkey=!AK7t-36P9nAec2Y&ithint=folder%2cexe

. . OK, I have downloaded AOK on machine 2 and installed with equal success. Now running on all cylinders.

. . OK, I have downloaded AOK on machine 2 and installed with equal success. Now running on all cylinders.

Thanks, Stephen. I've withdrawn Beta2 to avoid confusion.

I have good news, Beta 3 is working perfectly on the PNY LC 580 card, with 3 wu's at a time running, there are no wu's in the 'waiting to run' state, nor are there any wu's running real slow, all are running normally, now I have not seen a guppi run yet, but so far so good!

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I have good news, Beta 3 is working perfectly on the PNY LC 580 card, with 3 wu's at a time running, there are no wu's in the 'waiting to run' state, nor are there any wu's running real slow, all are running normally, now I have not seen a guppi run yet, but so far so good!

You say Beta 3 is running. However Beta3 isn't an application- all it is, is an installer.
Are you running CUDA or the SoG application?

---

Grant
Darwin NT

I have good news, Beta 3 is working perfectly on the PNY LC 580 card, with 3 wu's at a time running, there are no wu's in the 'waiting to run' state, nor are there any wu's running real slow, all are running normally, now I have not seen a guppi run yet, but so far so good!

You say Beta 3 is running. However Beta3 isn't an application- all it is, is an installer.
Are you running CUDA or the SoG application?

Sorry, My bad, SoG.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

There really isn't a AP CPU SSE4.1 app in this new beta Lunatics installer, correct? The installer defaults to old SSE4.1 app choice for AMD CPU as being preferred over AVX. However there is no SSE4.1 AP app now that Joe Segur left ... correct?? The SSE4.1 choice falls back on the older SSE3 AP app. We AMD users really should choose the AVX option as that one actually gets installed and is faster than SSE3. Once someone confirms my observation, I will rerun the installer and go back to the AVX app.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

There really isn't a AP CPU SSE4.1 app in this new beta Lunatics installer, correct?

Nope.
It's the same installer as the previous one, with the same applications as before with the addition of the SoG application.

As the original post says,

This is basically the v0.44 installer (64-bit only, to start with), with the following changes.

MB v7 legacy support removed
Cuda23 app removed (to make space in the user interface, only)
r3430 SoG app for NVidia included

Beta2 gave the choice of 32 or 64 bit installer & included the new r3430 ATI & Intel GPU versions
Beta3 uses the latest version of the NVidia SoG application- r3472

---

Grant
Darwin NT

The SSE4.1 choice falls back on the older SSE3 AP app. We AMD users really should choose the AVX option as that one actually gets installed and is faster than SSE3. Once someone confirms my observation, I will rerun the installer and go back to the AVX app.

Yes, it would be helpful if some AMD users could compare the speed of the AVX app with the 'best of the rest' - still only SSE3 so far.

If AVX turns out to be the best for AMD now, I'll disable the special selection for AMD and pre-select AVX when available - at least until somebody steps into Joe's shoes and completes the CPU app range.

I always have the dickens trying to find a specific task that just finished in my lists. Still trying to find examples of a MB task that used the SSE3 app versus my normal AVX app. I only was using the SSE3 app for a short while after trying the 0.45 Beta Lunatics installer. Any tasks that were completed with the SSE3 app in the past are long gone now to pick examples from. Just from my recollection .... the AVX app is about 15% faster on non-VLAR tasks and about 20% faster on VLAR tasks compared to SSE3. At least on my AMD CPU hardware. There needs to be more input from other crunchers to form a valid consensus probably before making a judgement call about changing the installer defaults.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Is there a way to get the r3472 app in the installer to identify itself in the Manager as either 8.00 or 8.12 version level? The newly formed app_info has both cases defined. I now have one machine using the 8.12 identifier from the manual installation of the app and the other machine still shows the 8.00 identifier in the Manager from using the beta installer. Now I have two different entries for the SoG app in BoincTasks which is sorta hard to read since they are listed in different places.

[Edit] Never mind, I see the other machine is starting to populate with 8.12 tasks.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

At least on my AMD CPU hardware. There needs to be more input from other crunchers to form a valid consensus probably before making a judgement call about changing the installer defaults.

Which looks to be AMD FX-8370 and FX-8350. I'm not familiar with how many AMD CPU types are AVX-enabled these days - but yes, I'd welcome additional input.

At least on my AMD CPU hardware. There needs to be more input from other crunchers to form a valid consensus probably before making a judgement call about changing the installer defaults.

Which looks to be AMD FX-8370 and FX-8350. I'm not familiar with how many AMD CPU types are AVX-enabled these days - but yes, I'd welcome additional input.

AFAIK all modern AMD CPU`s and APU`s are AVX enabled.

---

With each crime and every kindness we birth our future.