I've updated the AP part of optimized applications and now I don't get any new CUDA WUs. My app_info.xml :

<app_info>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>ap_5.00r103_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_win_SSE3_GPU_CPU_team.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<file_info>
<name>MB_6.08_mod_CPU_team_CUDA.exe</name>
<executable/>
</file_info>

<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
<file_ref>
<file_name>AK_v8b_win_SSE3_GPU_CPU_team.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>MB_6.08_mod_CPU_team_CUDA.exe</file_name>
</file_ref>
</app_version>

<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_v8b_win_SSE3_GPU_CPU_team.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>MB_6.08_mod_CPU_team_CUDA.exe</file_name>
</file_ref>
</app_version>


<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>607</version_num>
<file_ref>
<file_name>AK_v8b_win_SSE3_GPU_CPU_team.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>MB_6.08_mod_CPU_team_CUDA.exe</file_name>
</file_ref>
</app_version>

<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<file_ref>
<file_name>AK_v8b_win_SSE3_GPU_CPU_team.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>MB_6.08_mod_CPU_team_CUDA.exe</file_name>
</file_ref>
</app_version>

</app_info>

I've updated the AP part of optimized applications and now I don't get any new CUDA WUs. My app_info.xml :

<app_info>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>ap_5.00r103_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_win_SSE3_GPU_CPU_team.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<file_info>
<name>MB_6.08_mod_CPU_team_CUDA.exe</name>
<executable/>
</file_info>

<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
<file_ref>
<file_name>AK_v8b_win_SSE3_GPU_CPU_team.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>MB_6.08_mod_CPU_team_CUDA.exe</file_name>
</file_ref>
</app_version>

<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_v8b_win_SSE3_GPU_CPU_team.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>MB_6.08_mod_CPU_team_CUDA.exe</file_name>
</file_ref>
</app_version>


<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>607</version_num>
<file_ref>
<file_name>AK_v8b_win_SSE3_GPU_CPU_team.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>MB_6.08_mod_CPU_team_CUDA.exe</file_name>
</file_ref>
</app_version>

<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<file_ref>
<file_name>AK_v8b_win_SSE3_GPU_CPU_team.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>MB_6.08_mod_CPU_team_CUDA.exe</file_name>
</file_ref>
</app_version>

</app_info>

Have you gone to your Account page, Seti@home preferences and enabled astropulse_v5? By default it is set to no.

---

BOINC blog

Not sure if it's just happening to more than me, but since I have added ap_v5 to my app info, I haven't gotten any MBs, either. Non-CUDA.. 6.2.19, AK_v8_SSE3, ap500r103_sse3 and ap503r112_sse3. Went from ~250 MB's last week to only having 8 ap_v5's in my cache. That's all I've got.. just those 8 tasks.

3.0ghz P4 at work was sitting on 150+ MBs and it is down to 6 ap_v5's only.

I understand the splitters aren't quite holding up to speed like I thought they used to (I keep watching the creation rate, and it is always less than 1 per second), and I know the "ready to send" queue isn't always accurate, nor recent/current.

So that leaves one of two possibilities that I see.. 1) there's a scheduler bug for at least 6.2.19 (meaning it's server-side and not client-side..in light of all the 6.6.x work-fetch headaches); or 2) there just isn't any MBs to send.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Not sure if it's just happening to more than me, but since I have added ap_v5 to my app info, I haven't gotten any MBs, either. Non-CUDA.. 6.2.19, AK_v8_SSE3, ap500r103_sse3 and ap503r112_sse3.

How do you have the "Run only the selected applications" settings configured in SETI@Home preferences for the location associated with that host?

---

I've had to juggle between AP and MB on the Setiathome Preferences page in order to keep my CUDA pc stocked with the right amount of AP and MB for CUDA and AK_v8. When I start running low on MB, I just deselect all AP work on the preferences page till I get enough MB, and then reselect AP. When I finish the AP I have, I deselect MB til I get the amount of AP I want, and then allow MB again. After a couple of days I start the process oever again. This is with Boinc 6.4.6 (was the same for 6.4.5).

---

Not sure if it's just happening to more than me, but since I have added ap_v5 to my app info, I haven't gotten any MBs, either. Non-CUDA.. 6.2.19, AK_v8_SSE3, ap500r103_sse3 and ap503r112_sse3.

How do you have the "Run only the selected applications" settings configured in SETI@Home preferences for the location associated with that host?

MB, AP, AP_v5, allow for others are all checked.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

For what it's worth: since adding AP_V5, I've gotten almost all AP and AP_V5 WUs, only a couple of MBs.

---

I've had to juggle between AP and MB on the Setiathome Preferences page in order to keep my CUDA pc stocked with the right amount of AP and MB for CUDA and AK_v8.

I've been doing the same thing. It seems to me getting the scheduler to distinguish between CUDA and non-CUDA work for CUDA-capable clients should be a high priority.

---

--
Classic 82353 WU / 400979 h

It seems to me getting the scheduler to distinguish between CUDA and non-CUDA work for CUDA-capable clients should be a high priority.

Maybe app_info should mention MB app before Astropulse (by changing lines with MB section upper than AP section)?

It seems to me getting the scheduler to distinguish between CUDA and non-CUDA work for CUDA-capable clients should be a high priority.

Maybe app_info should mention MB app before Astropulse (by changing lines with MB section upper than AP section)?

I've got my MB listed first. The order in my app_info is MB, AP, AP_v5. I think with the structure of the app_info, it shouldn't matter what order the apps are listed (as long as the appropriate tags are listed immediately following the <app> declaration). I don't think it gets checked sequentially (from beginning to end) when it comes time to ask for more work.. it gets read at start-up and when requesting work, it tells the scheduler which apps you have, and the queues for all (three) apps are checked to see if there are WUs ready to send out. I think the order they ask for is MB, AP, AP_v5, but I could be wrong.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

As others have stated here I also have resorted to manually manipulating the settings of my "Run only the selected applications" in order to get the work I require. I have it set to Seti at Home only for 24 hours then disable that and enable both kinds of Astropulse for 24 hours. It seems to be the only way to get both kinds of work at this time. Also I use Boinc version 6.5.0. Any Boinc version higher than 6.5.0 will not properly request work for all projects at Seti.

---

Boinc....Boinc....Boinc....Boinc....

I ended up switching to my home preferences so I could get some MB work on my PC, plus I want to drop my pending down just a little bit from its 7X RAC level.

---

I think we wouldn't have that problem if AP was a separate project. We'd also be able to set a ratio between AP, MB and other projects to keep our CUDA devices busy.

---

I think we wouldn't have that problem if AP was a separate project. We'd also be able to set a ratio between AP, MB and other projects to keep our CUDA devices busy.

... at a cost to the SETI@Home staff of maintaining two of everything.

---

I ticked my v5 box and all of a sudden got two APS and no MBS. Makes you wonder if there is a fault ot just no MBs at the time to be sent.

---

Hm.. I think I may retract my claim of the possibility of some kind of scheduler logic on the server end. Maybe there just are no MBs available on a regular basis.

On one of my Linux boxes, I made a typo in the app_info and it rendered both of my AP selections useless, and the message log was showing

No work available for SETI@Home Enhanced
No work available for Astropulse
You have selected to receive work for other applications
No application available for Astropulse_v5


So, I think that kind of says there's no MB's available. Is it too much of a headache to turn those extra four splitters on that are always disabled?

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Another possibility since all the ready to send queses are full.

Since AP is now by default off for most users and the CUDA's are burning through the MBs at a fast rate, the 100 slot cashier's queue is now regularly filled with APV5's that very few are asking for leaving no space for MB's.

I realize that everyone loves to run as many WU's through as possible. If you look back you may recall the days of the old seti where people were lucky to get 2 or 3 WU's finished a day with a high powered 600mhz processor.

Nowadays it takes about 20 minutes to finish the WU on the newest CPU's What we seem to be forgetting is that its not the number of WU's we crunch but the data we generate. Also, Anyone that runs and finishes can calculate how much credit/ hour they get and can compare it to the MB WU's I can almost guarantee that the AP WU is generating more credit/hour than MB. Even greater so if you are running and opt app.

I can see very few reasons to not run the AP WU's if you receive one.
1) you can't possibly finish it within 3 days after its return date.
2) you are running a very slow PC. No crime there.
3) your desire for constant change compells you to abort a WU if it takes more than 2 hours.

I realize that some people will always abort the WU's and should be on their pages unclicking the appropriate places. I also realize that WU's may stay pending for a long time. I just got credit for a WU that I did in December. My wingman was running a xeon 2.0ghz CPU without the opt app. It took him almost 900,000 seconds. This gives me a warm fuzzy. Thats dedication and he got rewarded for his effort. The newer Wu's give and even bigger reward. I'd rather wait on a WU to get validated and get a major boost in credit than sit and collect 40 credits at a time.

I have around 100 AP's in my cache and no MB. It looks like I'll be knocking them out at around 15-16 hours a WU's on the opt ap. I the old 5.00 WU's ran at 11.8 hours which confirms that the 5.03's are running about 30% longer.

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

Hm.. I think I may retract my claim of the possibility of some kind of scheduler logic on the server end. Maybe there just are no MBs available on a regular basis.

On one of my Linux boxes, I made a typo in the app_info and it rendered both of my AP selections useless, and the message log was showing

No work available for SETI@Home Enhanced
No work available for Astropulse
You have selected to receive work for other applications
No application available for Astropulse_v5

So, I think that kind of says there's no MB's available. Is it too much of a headache to turn those extra four splitters on that are always disabled?

No, there are plenty of MB WUs around - just picked up about 500 across 4 hosts.

I think it's more to do with the feeder queues. Normally, I allow all WU types on all venues. I've been seeing that, when BOINC randomly contacts the servers to top up the caches, it seems to predominantly collect AP v5.03. But since I run CUDA, I can't exist on a diet of AP alone. So maybe once every other day (like today, before the outage), I disable AP_v5 on my application preference page, and briefly increase my cache from two days to three days. Never fails to get me plenty of CUDA-fodder, and then I can reset to normal knowing that the work balance will see me through until the next micromanagement session.

so the server isn't sending you WU's for your CUDA if you have the AP checked? that would be odd behavior on the server.

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope