Just made another update to the scheduler, let me know if anything has gotten better.

---

I still don't get any CPU work units:

13-06-12 13:28:31 | Milkyway@Home | update requested by user
13-06-12 13:28:32 | Milkyway@Home | Sending scheduler request: Requested by user.
13-06-12 13:28:32 | Milkyway@Home | Requesting new tasks for CPU
13-06-12 13:28:34 | Milkyway@Home | Scheduler request completed: got 0 new tasks
13-06-12 13:28:34 | Milkyway@Home | No tasks sent
13-06-12 13:28:34 | Milkyway@Home | No tasks are available for MilkyWay@Home
13-06-12 13:28:34 | Milkyway@Home | No tasks are available for Milkyway@Home Separation
13-06-12 13:28:34 | Milkyway@Home | No tasks are available for the applications you have selected.
13-06-12 13:28:34 | Milkyway@Home | Tasks for NVIDIA GPU are available, but your preferences are set to not accept them

It seem that there are no units available? My computer used to chew a lot of Separation work units, but the project status page (http://milkyway.cs.rpi.edu/milkyway/server_status.php) also shows none for Separation.

There shouldn't be any separation workunits, those should be under milkyway, as far as I know.

Agreed, but it looks like the problem is the scheduler doesn't have the STRAIGHT CPU APPLICATION configured any longer for Winboxes, if the Applications page is to be believed.

There doesn't seem to be a reference to the file:

milkyway_separation_1.00_windows_intelx86.exe,

in the MilkyWay@Home section, which is the one you need to run MW on the CPU.

There should be a line with this information for 32 bit Winboxes:

Platform: Microsoft Windows (98 or later) running on an Intel x86-compatible CPU

Version: 1.00 <---- Note: NO plan_class

Installation Date: 08-Feb-2012, 17:08 UTC.


And for 64 bit Winboxes (milkyway_separation_1.00_windows_x86_64.exe):

Platform: Microsoft Windows running on an AMD x86_64 or Intel EM64T CPU

Version: 1.00 <---- Note: NO plan_class

Installation Date: 08-Feb-2012, 17:08 UTC.

This Information used to be on the Applications page, but has disappeared with the recent upgrades and updates.

[Agreed, but it looks like the problem is the scheduler doesn't have the STRAIGHT CPU APPLICATION configured any longer for Winboxes, if the Applications page is to be believed.

There doesn't seem to be a reference to the file:

milkyway_separation_1.00_windows_intelx86.exe,

in the MilkyWay@Home section, which is the one you need to run MW on the CPU.

There should be a line with this information for 32 bit Winboxes:

Platform: Microsoft Windows (98 or later) running on an Intel x86-compatible CPU

Version: 1.00 <---- Note: NO plan_class

Installation Date: 08-Feb-2012, 17:08 UTC.


And for 64 bit Winboxes (milkyway_separation_1.00_windows_x86_64.exe):

Platform: Microsoft Windows running on an AMD x86_64 or Intel EM64T CPU

Version: 1.00 <---- Note: NO plan_class

Installation Date: 08-Feb-2012, 17:08 UTC.

This Information used to be on the Applications page, but has disappeared with the recent upgrades and updates.

Yeah, I just fixed this. Any better now?

---

Yeah, I just fixed this. Any better now?

Just did a few manual updates, requested work, none sent. I did note the apps are now listed again though.

I've been getting a steady stream of v1.02 (opencl_amd_ati) work since 13 Jun 2013, 1:58:56 UTC.

---

Just curious: Why both single-thread and multi-thread apps? I am getting sent both, and that leads to idle threads. For example, on an 8 thread machine, I get sent 5 ST tasks and 5 MT tasks. When the ST tasks run, it leaves 3 threads idle. And BOINC won't ask for more ST threads because it thinks it already has enough work due to the queue of MT tasks.

If both apps will stay, how about a way to select one or the other on our preference page, like we can do with GPU types?

---

A workunit is flagged with "4 CPUs" and will not start unless I set preferences to use all 4 processors on my system.

I normally allow 2 processors (out of 4) to work on SETI and Milkyway projects during the day and allow 4 processors when I leave the office.

Right now nothing is running during the day because of this "4 CPU" setting, I am assuming, and no other work from either project has been scheduled for me because of the size of this workunit for Milkyway - 700+ hours.

A workunit is flagged with "4 CPUs" and will not start unless I set preferences to use all 4 processors on my system.

I normally allow 2 processors (out of 4) to work on SETI and Milkyway projects during the day and allow 4 processors when I leave the office.

Right now nothing is running during the day because of this "4 CPU" setting, I am assuming, and no other work from either project has been scheduled for me because of the size of this workunit for Milkyway - 700+ hours.

Tasks are assigned the number of CPUs at the time of the download. So you had all 4 CPUs available when those MW tasks were downloaded. No way to change that to 2, after the tasks have been downloaded, aside from deleting them and downloading fresh tasks with your settings to allow only 50% CPU. After downloading, you can change your settings to use 100%. The MT tasks will still use only 2 cores. Of course, the scheduling logic may cause BOINC to run two MW tasks, or 4 SETI tasks, or 1 MW task and two SETI tasks.

---

A workunit is flagged with "4 CPUs" and will not start unless I set preferences to use all 4 processors on my system.

I normally allow 2 processors (out of 4) to work on SETI and Milkyway projects during the day and allow 4 processors when I leave the office.

Right now nothing is running during the day because of this "4 CPU" setting, I am assuming, and no other work from either project has been scheduled for me because of the size of this workunit for Milkyway - 700+ hours.

Tasks are assigned the number of CPUs at the time of the download. So you had all 4 CPUs available when those MW tasks were downloaded. No way to change that to 2, after the tasks have been downloaded, aside from deleting them and downloading fresh tasks with your settings to allow only 50% CPU. After downloading, you can change your settings to use 100%. The MT tasks will still use only 2 cores. Of course, the scheduling logic may cause BOINC to run two MW tasks, or 4 SETI tasks, or 1 MW task and two SETI tasks.

I can't find where I read it anymore but I "heard" that that may be changing in some future version of Boinc! I am guessing not any time soon, but who knows. What I "heard" was that we may be able to set our pc's cpu cores, for example, to run one Seti unit 24/7, while at the same time running one Malaria unit and 2 MW units, and never have that change. Giving the user more control of what projects they crunch for and how much work they provide for it. No more overall percentage numbers, more physical numbers.

Now whether that could, or would even work, be translated to the gpu is another question entirely. But could be interesting too.

I would love to have that sort of control.

I would love to have that sort of control.

I seem to remember the person talking about Boinc 8 or above, but it was a while back now, one small blurb of a comment and then no more. I am guessing they keep things pretty close to the vest as far as future implementations. I mean what if they say this or that is coming, and it doesn't?!