,and i let the miners cool the metalplate on a servercase.I clock them now on 2Gh ,and they ran fine around 2Gh the past 24 hrs.
The worker shows a avg of 4Gh
So also extra cooling seems to contribute a lot
Topic: Antminers & Workers (Read 1032 times)
I restarted the "rig" ,and i let the miners cool the metalplate on a servercase.
I clock them now on 2Gh ,and they ran fine around 2Gh the past 24 hrs.
The worker shows a avg of 4Gh
So also extra cooling seems to contribute a lot
,and i let the miners cool the metalplate on a servercase.I clock them now on 2Gh ,and they ran fine around 2Gh the past 24 hrs.
The worker shows a avg of 4Gh
So also extra cooling seems to contribute a lot
Also, I'd look to see what sort of time-frame the average is calculated over. For instance, on Eligius, the 3-hour average is much more accurate than the 128 second average, since the number of shares submitted is used to calculate the average, and in a very short time-sample, it's not granular enough to give you accurate results.
What pool are you using? It could be possible that your pool calculates your hash rate based on share submitted. So if your unlucky you could just have been just submitting not very many shares.
Hi,
I have a Raspberry running on cgminer with 2 Antminers U1.
Each Antminer reports about 2 Gh/s speed, so that's ok.
However pooling on bitcoinCZ the site reports avg 1461 Mh/s that is less than 1 miner does.
Both miners run on 1 worker, should you configure each miner on a worker?
How do i get "up to speed" ?
I have a Raspberry running on cgminer with 2 Antminers U1.
Each Antminer reports about 2 Gh/s speed, so that's ok.
However pooling on bitcoinCZ the site reports avg 1461 Mh/s that is less than 1 miner does.
Both miners run on 1 worker, should you configure each miner on a worker?
How do i get "up to speed" ?
Jump to: