Client Priority

[goobee]

Even though I have priority set at "0", the dnetc client will not let go when I want to do something on my machine. I wind up having to turn off the client to be able to work and then I forget to turn the client back on. Any suggestions on how to get the client to automatically let go? I am using the 64bit Widows client.
_________________

[Polo]

I've never used this platform...
But I never had this kind of problem with the client on winXP 32 bits or Linux 32 or 64 bits.

If you want, you can tell the client to not run on every CPU core by adding :

[processor-usage]
max-threads=3

in your dnetc.ini file.
If your processor is HT capable then max-thread = (number_of_core X 2) - 1

Or perhaps a bug in the client version ? Try another one :
Here is the last RC client (v2.9110.519b ): http://http.distributed.net/pub/dcti/prerelease/rc/dnetc519b-win64-amd64.zip
Here is the last client (V 2.9109.518) : http://http.distributed.net/pub/dcti/current-client/dnetc-win64-amd64.zip
_________________
Have fun and sport !

[goobee]

That makes a whole bunch of sense. I let the client auto detect and configure itself. It sees the i7 930 as having 8 cores and assigned 8 threads. Since it's only 4 actual cores and 4 via hyperthreading, even if it throttled down by 50%, it would still be close to maxing out the processor.
_________________

[Polo]

On my machines the client is also auto detecting and configuring. But all goes well.
I have experienced problems on a winXP machine trying to crunch with both CPU and GPU. The machine wasn't running smoothly anymore... much more like a turtle... so I let it crunch only with the CPU and all went back to normal operation.
_________________
Have fun and sport !

[goobee]

I think my 17 930 is getting tired. I know my vid card, a GTX 285 is getting long in the tooth as well.
_________________