• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Maximizing RC5 keyrate

MereMortal

Golden Member
What is the best way to get the keyrate back up after using a CPU intensive application? I noticed it takes its good old time making its way back to the max rate. Does restarting the client help? Rebooting? Something else?

The OS I'm running is WinME if it makes a difference. My apologies if this is a naive question, but a long day at work has left my brain oozing out my ear. 😕
 
On my systems soon as I exit whatever is using the CPU RC5 climes right back up to 99% usage. Im running Win2k but that shouldn't matter. How long of a delay is there until te client goes back to peak CPU usage?
 
You might want to use Wintop or Another Task Manager to check what processes are running during these 5 hours. ATM will aloow you to nuke some or change their priority (with ATM, make sure that you disable its cpu cooler, you'll see why when you do it and look at cpu useage).
 
MereMortal, you are a little confused...

The cracking rate displayed in the client window is an AVERAGE. That means, if you play Unreal Tournament for 2 hours and the crack blocks uninterrupted for 2 hours, the key rate should show to be HALF your maximum rate at the end of the total 4 hours.

If you shut down the client and restarted it, the average would reset and you would see your maximum keyrate displayed, but it is really not necessary.

JHutch
 
There are 2 keyrate stats that will be displayed after completing a block, the average and the rate for that block. The average will, of course, gradually go back towards normal after closing an intense application. The block after the one that was abused during that program's duration should reflect your standard keyrate.
 
Ok, thanks. I didn't realize that was an average rate. Over how long is this average taken, though? My max average keyrate is 3.15 Mkeys/s. When I first made this post, the average was down 3.03 Mkeys/s with 99% CPU. Now, almost 9 hours later, the average is only up to 3.10 Mkeys/s. Am I just being too obsessive about the keyrate?
 
<<Am I just being too obsessive about the keyrate? >>

Probably 😀!

However I periodically run RC5 benchmarks just to make sure everything is OK, that shupld give you some reassurance the client is capable of running full speed.
 
The average is an average since the last time the client was started. For some people, that average can be an average over MONTHS... 🙂

I've got one machine at home with around a 2 month up time. The only thing that took it down even then was a thunderstorm! 🙂

JHutch

PS And you can never get too obsessive about stats!
 
Well, it's either obsessing about RC5 or obsessing about my thesis. And the former is much more fun than the latter. Anyway, I will stop worrying about this average keyrate and start worrying about more important matters--like buying a router and getting my old system cracking! 🙂
 
Back
Top