Bitcoin Forum
May 09, 2024, 08:50:13 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Why am I getting 923.18 Gh/s from Antminer S3 and S1?  (Read 737 times)
paramind22 (OP)
Hero Member
*****
Offline Offline

Activity: 2646
Merit: 550


View Profile WWW
November 15, 2016, 04:23:59 AM
 #1

I just noticed at my pool I'm getting 923.18 Gh/s from my Antminer S3 and S1.  I got them used
and I don't know about any overclocking settings on them.  The Gh/s should be around 575 to 700. 
I'm using Eliguis for the pool. 

The trust scores you see are subjective; they will change depending on who you have in your trust list.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715287813
Hero Member
*
Offline Offline

Posts: 1715287813

View Profile Personal Message (Offline)

Ignore
1715287813
Reply with quote  #2

1715287813
Report to moderator
paramind22 (OP)
Hero Member
*****
Offline Offline

Activity: 2646
Merit: 550


View Profile WWW
November 15, 2016, 04:25:36 AM
 #2

I just rechecked the settings and its now at 273.54 Gh/s.  

and a few minutes later now 718.03 Gh/s.  I'm not worried just wonder what the pool mechanics are that do this and that it's not on my side but something happening at the pool.

gt_addict
Hero Member
*****
Offline Offline

Activity: 2492
Merit: 621


View Profile
November 15, 2016, 06:14:38 AM
 #3

This is perfectly normal. All mining machines do it. It's just a variation on how quickly the chips are processing the work. When you have a look on the GUI it will read the correct Ghs and also on the pool it will read the correct Ghs on each shift.

**SUPPORT SIDEHACK** Miner Development Donations to:  1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr

Donations/Tips to:-   1GTADDicTXD1uachKKgW24DZDxDGhSMdRa

Join Bitconnect: https://bitconnect.co/?ref=gtaddict
unholycactus
Legendary
*
Offline Offline

Activity: 1078
Merit: 1024



View Profile WWW
November 16, 2016, 10:42:08 PM
 #4

Your sample size to evaluate your hashing was simply not big enough.
You probably just started them and recorded a spike.

You're right to say that over a long period of time it should be around 600 or a bit less.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!