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

Rate changes in ECCp-109 client

MereMortal

MereMortal

Golden Member
I've noticed some odd behavior from the ECCp client on my T-Bird 1330@1500. When I start the client I get 670k ips, but the rate jumps to 705k ips whenever I attempt to send dp's (and stays at the higher rate thereafter).

Anyone else notice this type of behavior? Or know a reason for the jump?
 


<< Anyone else notice this type of behavior? Or know a reason for the jump? >>



I have noticed the behavior. In the function 'iterate' the operation performed on a point is dependent on the value of the point, so it is possible for this to happen. The first time I noticed this I thought something was broke until I took a closer look at the code.

I have also noticed that it is possible to find zero DPs in any given hour, but the daily average number of DPs per CPU usually does not vary too much.

Also, if you use the Linux client please keep in mind that the client does not perform a save when you use Ctrl-C to shut down the client. In one of the source code files the author mentions that the correction is on his to do list.

670K its/sec, man that is very nice 🙂 <envy> 🙂
 
I may have to take a look at the source code.

I would not be wary about this if the it/sec fluctuated from the lower to upper bounds. However, this result is entirely dependent upon my clicking on the send results button the first time.

I guess maybe I don't thoroughly understand what you are saying, or maybe I just didn't do a very good job explaining the situation in the first place (Sorry, I'm trying to function on 4 hrs sleep). So I will try again.

I start the client and it happily plugs along at 667k +/- 5k it/sec. Then I click the send results button for the first time (no permanent connection) and, whether or not the send was successful, my rate instantly jumps to 702k +/- 5k it/sec and stays in this new range until I stop/restart the client. I just thought a sudden increase of 35k it/sec was strange. The client always does this after a fresh restart, and I always get the same jump no matter how long I let it plug away before trying to send in dp's. Either the output it/sec isn't very accurate (or doesn't mean much) or there is something in the code that causes this jump after sending. I guess I need to have a look at the code.

Anyway, thanks for your reply. 🙂
 
MereMortal after reading your detailed description I now wonder if something might be awry.
You can post your question here and someone should be able to confirm if this is indeed a bug.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top