GPUGRID is now requesting less than one processor such that people can run a further cpu job.
This will stay if there are no problems. People should not use ncpus anymore and update to clients 6.3.19.

GDF

Nice! I'll try this later @ home and report... :)

GPUGRID is now requesting less than one processor such that people can run a further cpu job.
This will stay if there are no problems. People should not use ncpus anymore and update to clients 6.3.17 or 6.3.14.

GDF

I would say use 6.3.17. So far no problems. I did extensive testing with 6.3.15 with no problems as far as job scheduling, testing both CPU=1 and CPU<1 jobs, which always ran and ran the proper number of other CPU only jobs. 6.3.17 should be the same as far as that goes.

6.3.14 will work some, but eventually it will leave no GPU tasks running, or only a GPU running. It does not behave well.

Any idea when 6.3.17 for Linux64 will be out ? 6.3.14 won't work for me...

Any idea when 6.3.17 for Linux64 will be out ? 6.3.14 won't work for me...

No I don't, but usually once the windows version is released to alpha, which is was on Friday, the linux version follows in a few days. Being that it is now the week-end I would guess not at least until Monday.

Hehe, yea it's now <1...
BOINC shows 0.90 CPUs, 1 CUDA.

BOINC also shows 4 CPU tasks running plus 1 PS3GRID, but the taskmanager shows:

3 Einstein tasks with each 25% CPU
1 Cosmo task with 25%
and all few seconds I can see the acemd task kicking in with 1 or 2% CPU.

Is this how it should work?
I would think with 0.9 CPU the PS3GRID task should get more of the CPU?

[edit]Using 6.3.17, of course without ncpus+1[/edit]

---

pixelicious.at - my little photoblog

Do we need to wait for new work for this to take affect?

I am seeing "Running (1.00 CPUs, 1 CUDA)" on 6.3.17

0.9 is only indicative, as long is less than 1.

gdf

Please check ms/step to see if they change.

gdf

Hehe, yea it's now <1...
BOINC shows 0.90 CPUs, 1 CUDA.

BOINC also shows 4 CPU tasks running plus 1 PS3GRID, but the taskmanager shows:

3 Einstein tasks with each 25% CPU
1 Cosmo task with 25%
and all few seconds I can see the acemd task kicking in with 1 or 2% CPU.

Is this how it should work?
I would think with 0.9 CPU the PS3GRID task should get more of the CPU?

[edit]Using 6.3.17, of course without ncpus+1[/edit]

my task manager shows 3 ramsey WUs at 25%, 1 at 17-18% and the GPU app at 7-8%

Hehe, yea it's now <1...
BOINC shows 0.90 CPUs, 1 CUDA.

BOINC also shows 4 CPU tasks running plus 1 PS3GRID, but the taskmanager shows:

3 Einstein tasks with each 25% CPU
1 Cosmo task with 25%
and all few seconds I can see the acemd task kicking in with 1 or 2% CPU.

Is this how it should work?
I would think with 0.9 CPU the PS3GRID task should get more of the CPU?

[edit]Using 6.3.17, of course without ncpus+1[/edit]

Yes, that is correct behavior.

The 0.9 can be any number less that 1.

If you check all CPU only jobs will run at low system priority.
CUDA/CPU=1 will run at low system priority
CUDA/CPU<1 will run at normal system priority.
This is for windows, i do not know how linux call it, but CPU<1 should run at a higher priority than the others.

In the future when there are more projects and more GPU's the CPU<1 percentage will matter, but for now with only one project it does not, as long as it is less than 1. I think the goal will be to use up to physical CPUs + 0.99

Do we need to wait for new work for this to take affect?

I am seeing "Running (1.00 CPUs, 1 CUDA)" on 6.3.17

Yes, any exsiting work you have will run at what ever it was sent at. You will notice the change was new work starts to download, although there may still be some work in the server queue at the old setting.

The 6.3.17 is working fine.

One Problem with vista 64. Without admin rights only three task + ps3grid are running on a quad. With admin rigts there are 4 task + ps3grid running.

any help?

---

Constant dripping wears away the stone. :)

Yes, that is correct behavior.

The 0.9 can be any number less that 1.

If you check all CPU only jobs will run at low system priority.
CUDA/CPU=1 will run at low system priority
CUDA/CPU<1 will run at normal system priority.
This is for windows, i do not know how linux call it, but CPU<1 should run at a higher priority than the others.

In the future when there are more projects and more GPU's the CPU<1 percentage will matter, but for now with only one project it does not, as long as it is less than 1. I think the goal will be to use up to physical CPUs + 0.99

Ok...
I'm only looking at the Vista host now, because it is more critical.
On the Linux hosts I still use ncpus+1 until the new setting hits them too...


I just checked the priority and the PS3GRID task was running at the lowest priority. After restarting BOINC the acemd task is now running at normal priority, and still shows the same behaviour. CPU only tasks get ~25% (one full core) and ps3grid only gets one or two percent CPU all few seconds...
Let`s see if the ms/step changes after the first few results...

---

pixelicious.at - my little photoblog

The 6.3.17 is working fine.

One Problem with vista 64. Without admin rights only three task + ps3grid are running on a quad. With admin rigts there are 4 task + ps3grid running.

any help?

Get rid of vista.

Sorry its been a long day...

No, I don't know about that one. I'll inquire on the alpha testers list.

ps, for those with the startup wizard attach problem, i've inquired on that too.

Admin rights shouldn't be necessary!

I have 4 CPU tasks plus one GPU running on my Vista64 box. Just wait a little bit until the next task switch, the changes don't happen immediately. Or maybe restart BOINC...

---

pixelicious.at - my little photoblog

Admin rights shouldn't be necessary!

I have 4 CPU tasks plus one GPU running on my Vista64 box. Just wait a little bit until the next task switch, the changes don't happen immediately. Or maybe restart BOINC...

That is what I would think too, but it should kick in another task right away. I have not seen since 6.3.15 any improper number of tasks running on three windows XP clients, always immediately another one will start, or download more work if necessary and start. I've tried many things to break the scheduler and have not been able to. I've tired many combination of projects, cache size, cpus, suspended tasks, suspended project, and so on. Most always it will change immediately or within 2 seconds at most.

Now for Linux I have a Q9550 running 4 cpu tasks and the gpu is always waiting to run 0.90 cpu,1 CUDA ????It starts up correctly but in 30 seconds or so it switches the CUDA app to waiting to run. Tried BOINC 6.3.10 & 6.3.14 same effect, Also the system monitor is showing only about 80% of resources are being used.My other Q9550 box is running correctly 4 cpu's and 1 0.90cpu,1CUDA for 5 total threads and 100% utilization...

What happenned? What can I do?

Hmm... Now I also have only 3 CPU tasks and one GPU task running...

I'll set up cc_config with a few debug flags tomorrow morning to set what's happening.

---

pixelicious.at - my little photoblog

Now for Linux I have a Q9550 running 4 cpu tasks and the gpu is always waiting to run 0.90 cpu,1 CUDA ????It starts up correctly but in 30 seconds or so it switches the CUDA app to waiting to run. Tried BOINC 6.3.10 & 6.3.14 same effect, Also the system monitor is showing only about 80% of resources are being used.My other Q9550 box is running correctly 4 cpu's and 1 0.90cpu,1CUDA for 5 total threads and 100% utilization...

What happenned? What can I do?

Nothing. Client flaws.

In my testing (all on windows), the CPU<1 only works correctly in 6.3.15, 6.3.16 and 6.3.17.

6.3.14 and 6.3.10 had flaws which prevented the correct behavior. Sometimes it might work, but more often not, leaving less than max cpus or no gpu task running.

@stefan
Which version client are you running ?

@GDF
Maybe you should wait until an official 6.3.17 linux is made, as the last one I see is 6.3.14 on the dl page. Maybe you should switch back to CPU=1 until one is released, unless you have one all linux users can download.