• 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.

I am having difficulties with RC5

John

Moderator Emeritus<br>Elite Member
Guys, I have a 1.5GHz Tbird, and run Win 2K. When I reboot I am usually cracking [5.10 Mkeys/s]. However if I play UT for a while and quit, then I check the RC5 status I am at [1.85 Mkeys/s]

What's happening? I do not have any weird TSR's running either. However I run the benchmark and get the following:


[May 18 05:15:55 UTC] Benchmark for RC5 core #6 (RG/HB ath)
0.00:00:16.00 [5,504,030.21 keys/sec]
.....10%.....20%.....30%.....40%.....50%...
[May 18 05:16:26 UTC] Benchmark for RC5 core #6 (RG/HB ath)
0.00:00:08.18 [5,510,927.28 keys/sec]


What is happening to my rate?
 
John, is your keyrate *staying* depressed after playing UT? It's normal for it to drop when the CPU is working hard on something, but not normal for it to stay that way afterwards. Since the keyrate is reported for the rate at which the whole packet was done, rather than the instantaneous rate at the end, a packet that was being slowed down by UT will report a low keyrate, but the next packet should be reporting normal keyrate. Fill us in on what it's doing?
 
Happens all the time on my T-Bird W2K box. Happened on the P3 too. The problem is that if you have lots of tasks running, they will grab the cycles instead of the client - priority levels if you will. If you've ever used &quot;nice&quot; in Linux it's a very good analogy as to what I'm trying to explain here.

Noting above I'm guessing the problem is with the client or OS not sending the cycles it lost back to the client before the applications took over those CPU cycles. However, at times I have also seen the client revive itself and it starts cracking at its normal rate again. ... Let it crack for a while and it should come back to it's normal rate.

If not, right-click the cow and hit restart.
 
I have a similar problem, I talked about this earlier..

I leave my computer running all the time, and say I come to use it for something.. even like getting on napster, and chatting for say 10 minutes on ICQ, I then leave my computer, and come back say 20 hours later, and the rate has dropped, and stayed down all that time.

The only fix is a reboot.. *shrug*

WinMe here.

As I said in my previous post, I am a lucky one with great success.. I only reboot now mostly to keep my rate up.. WinMe runs amazingly for me.
 
Remember there are two rates reported, one for the package (1.542 in my case) and one average (1.53) for the whole session.
[May 18 09:31:04 UTC] Completed RC5 packet 31E81A6F:B0000000 (32*2^28 keys)
0.01:32:48.76 - [1,542,531.49 keys/sec]
[May 18 09:31:04 UTC] Loaded RC5 27*2^28 packet 321B8B67:E0000000
[May 18 09:31:04 UTC] Summary: 81 RC5 packets (211*2^28 keys)
0.10:11:02.87 - [1.53 Mkeys/s]
 
Back
Top