Does anyone have the weird problem where normal clocked s3's give 440 GH/s quite well, and overclocked S3's (to 250), give...440 Gh/s?
They do seem to start out faster, with a higher rate initially, but always seem to go back down to this level. I just don't understand why they would do that. Hardware errors are low in all cases. I'm using P2Pool, but I don't think that should have anything to do with it. Does anyone shed some light on the issue?
From my testing they don't seem to show this behavior if you keep them cold, and I mean cold. I stuck a unit that would do 250 for 1-2h and then started falling in performance in front of a portable AC and got the load temps below 25C, it seemed to be just fine at 495GH/s+ under those temps (12h~ of testing) but not really worth it with the AC costs ;P
Or maybe it's just random behavior and it will drop the has hash rate despite the cooling given enough time, someone will figure these out eventually :/