Eh? Client not running at full steam?

[MooCow]

For some reason the system idle process is getting MORE cpu time than my client all of a sudden. I haven't changed anything that I know of.[Oct 06 17:48:41 UTC]

Completed RC5 packet D4134376:B0000000 (30*2^28 keys)
0.05:48:59.53 - [384,586.48 keys/sec]
[Oct 06 17:48:41 UTC] Loaded RC5 32*2^28 packet D452FDD0:60000000
[Oct 06 17:48:41 UTC] Summary: 3 RC5 packets (36*2^28 keys)
0.06:38:40.93 - [381.24 kkeys/s]
[Oct 06 17:48:41 UTC] 339 RC5 packets (2468 work units) remain in
buff-in.rc5
[Oct 06 17:48:41 UTC] Projected ideal time to completion: 16.07:27:08.00
[Oct 06 17:48:41 UTC] 1 RC5 packet (30 work units) is in buff-out.rc5
.....10%.....20%.....30%.....40%.....50%....
[Oct 06 20:08:28 UTC] Benchmark for RC5 core #2 (RG class 6)
0.00:00:08.01 [654,422.63 keys/sec]
.....10%.....20%.....30%.....40%.....50%....


had been getting about 630 keys/sec normal, what gives?

 

[GT1999]

Are you running under NT or 9x? You might want to bump the PID up for dnetc.exe and see if that works (there's an option in the client). They say not to mess with it, give it a little more priority than the default setting.

G|T

 

[MooCow]

didn't even think of that, I'm running win2k pro, with client 2.801 I suppose I could bump up the PID a bit, I'll see how that does...thanks!

 

[JonB]

MooCow, I'd look for other problems before the PID or priority. My Win2K shows 20 hours for DNet and 2 minutes for System Idle Process.

Instead, look at virus checkers or Defragmenters or FindFast. Defragmenters will put Dnet to sleep while they run, and they don't use 100%, so Idle time will build up. My AntiVirus will put DNet to sleep also.

Look in your DNet ini file for "triggers" like:

[triggers]
pause-watch-plist=navwnt.exe|dfrgntfs.exe

[edit]
You might want to log CPU activity for various tasks. Something is running; you just need to find out when. As I look at your log file, I don't see it pausing for my earlier guesses.

 

[TheJoker]

Well one thing that I have noticed and I'm running win2k pro on my main system is that after a while of running different apps the dnet client doesn't run at full steam. That's after all the other apps have been closed. If I close the dnet client and restart it I'm back to normal. Has anyone else noticed this?

 

[GT1999]

Yep, exact same thing happens on my system. But if you let the client sit alone for a while, it picks back up again.

G|T