so how you gonna say it's better one way or the other when the Client doesn't obey what your settings are ???

I only have QMC running along GPU-Grid and after the initial startup phase I've never seen it drop to 3+1, that's why I think my current times are indicative for 4+1.

I have a 1.25 days cache and have set GPU-Grid to 31% ressource share and I don't have any problems with running dry on CPUs.

MrS

---

Scanning for our furry friends since Jan 2002

I don't have any problems running out of work either, that's not the issue here. The issue for me anyway is I can't get the Client to run what I want it to run. No matter what I set it to it does what it wants to do.

I really only want to run 3 CPU Wu's plus 1 GPU Wu so I set it to <ncpus>4</ncpus> which should give me what I want. But when I look most of the time it's running 4 CPU Wu's & 1 GPU Wu on all my CUDA Capable Box's. So unless I'm putting the wrong command in the <ncpus></ncpus> line in the cc_config.xml file the Client isn't doing what it's told to do, Thats the issue.

My times for the GTX 260's I have vary by as much as 2-3 hr's because of this problem ... :)

Hang in there PoorBoy, This can't stay ALPHA forever...

I haven't been playing with the <ncpus> option. I normally just use the 'max cpu's' in the project profiles I am running (Home, werk,...). Set it to 3 (for my quad) and let 'er rip. That has let me run 3+1 or 4+1 whenever I want (as long as the developers don't mess with the server settings..again..lol).

And so far my Linux64 GPU box runs 1-2% cpu usage on 3+1 and 4+1, so I don't bother changing any more. I'll have to recheck my Win64 box again to see if that is any different.

---

Consciousness: That annoying time between naps......

Experience is a wonderful thing: it enables you to recognize a mistake every time you repeat it.

I don't have any problems running out of work either, that's not the issue here. The issue for me anyway is I can't get the Client to run what I want it to run. No matter what I set it to it does what it wants to do.

I really only want to run 3 CPU Wu's plus 1 GPU Wu so I set it to <ncpus>4</ncpus> which should give me what I want. But when I look most of the time it's running 4 CPU Wu's & 1 GPU Wu on all my CUDA Capable Box's. So unless I'm putting the wrong command in the <ncpus></ncpus> line in the cc_config.xml file the Client isn't doing what it's told to do, Thats the issue.

My times for the GTX 260's I have vary by as much as 2-3 hr's because of this problem ... :)

If you want to limit cpus, you should try setting in global preferences the cpus to 1 less than your max. If you read the description of ncpus in the wiki, it tells you this, it is for simulation more cpus than you have, not limiting less than max.

The only problem is the client, so no matter what you do currently, it won't matter much. It has a bug and malfunctions at times. The logic for task pre-emption in the client is backwards. It behaves differently depending on a lot of factors, number of projects, resource shares, amount of work, deadlines, etc. In other words it preempts the wrong task. There is not much you can do except wait. I found the bug and reported it. A fix was checked in, we are just waiting on a new build.

I've tried that too, setting my ncpu's to 3, problem is thats all it run's sometimes is 3. Two Regular Wu's & 1 GPU Wu ...

Well, while we are waiting for version 6.3.21, I've decided to try to build my own. I've read the directions and begun downloading all the parts I need. Although I will have to do the actual build when I get home, later tonight or the weekend. This way I can begin testing the fixes when made before a release and see if they bugs are fixed.

Then I Checked the timeline and Rom, two minutes ago tagged a release for 6.3.21.

So a new version will be ready very very soon.

***** Note however it is untested. I do not know if it will work correctly yet. Use at you own risk. *****