Only Getting around 5-27 GH/s with Butterfly 50GH/s Unit

[renfors]

Hi,

With deepbit: 5.5 GH/s
With btcguild: 27.3 GH/s

Pretty far from 50 GH/s, am I doing something wrong?
Should I look for something special in the mining-pools to decide if I will be able to run at full speed?
My network connection is from a 3G connection (that works ok for surfing and streaming video), could a better connection make a difference?
Have tried to ask about this at the Butterfly forum but didn't get any response.

 BTC Guild:
 [2013-11-25 07:22:08] Started at [2013-11-25 04:56:02]                   
 [2013-11-25 07:22:08] Pool: http://eu-stratum.btcguild.com:3333                   
 [2013-11-25 07:22:08] Runtime: 2 hrs : 26 mins : 5 secs                   
 [2013-11-25 07:22:08] Average hashrate: 27368.8 Megahash/s                   
 [2013-11-25 07:22:08] Solved blocks: 0                   
 [2013-11-25 07:22:08] Best share difficulty: 111K                   
 [2013-11-25 07:22:08] Share submissions: 1540                   
 [2013-11-25 07:22:08] Accepted shares: 1519                   
 [2013-11-25 07:22:08] Rejected shares: 21                   
 [2013-11-25 07:22:08] Accepted difficulty shares: 48578                   
 [2013-11-25 07:22:08] Rejected difficulty shares: 432                   
 [2013-11-25 07:22:08] Reject ratio: 1.4%                   
 [2013-11-25 07:22:08] Hardware errors: 727                   
 [2013-11-25 07:22:08] Utility (accepted shares / min): 10.41/min                   
 [2013-11-25 07:22:08] Work Utility (diff1 shares solved / min): 347.20/min
                   
 [2013-11-25 07:22:08] Stale submissions discarded due to new blocks: 0                   
 [2013-11-25 07:22:08] Unable to get work from server occasions: 0                   
 [2013-11-25 07:22:08] Work items generated locally: 57088                   
 [2013-11-25 07:22:08] Submitting work remotely delay occasions: 1                   
 [2013-11-25 07:22:08] New blocks detected on network: 24
                   
 [2013-11-25 07:22:08] Summary of per device statistics:
                   
 [2013-11-25 07:22:08] BAL0                | (5s):27.46G (avg):27.37Gh/s | A:48578 R:432 HW:727 WU:347.2/m                   
 [2013-11-25 07:22:08]                     


DeepBit:
[2013-11-25 01:24:24] Started at [2013-11-24 16:47:30]
[2013-11-25 01:24:24] Pool: Bitcoin mining pool
[2013-11-25 01:24:24] Runtime: 8 hrs : 36 mins : 54 secs
[2013-11-25 01:24:24] Average hashrate: 5507.6 Megahash/s
[2013-11-25 01:24:24] Solved blocks: 0
[2013-11-25 01:24:24] Best share difficulty: 12.8K
[2013-11-25 01:24:24] Share submissions: 40490
[2013-11-25 01:24:24] Accepted shares: 40319
[2013-11-25 01:24:24] Rejected shares: 171
[2013-11-25 01:24:24] Accepted difficulty shares: 40318
[2013-11-25 01:24:24] Rejected difficulty shares: 171
[2013-11-25 01:24:24] Reject ratio: 0.4%
[2013-11-25 01:24:24] Hardware errors: 273
[2013-11-25 01:24:24] Utility (accepted shares / min): 78.02/min
[2013-11-25 01:24:24] Work Utility (diff1 shares solved / min): 0.00/min

[2013-11-25 01:24:24] Stale submissions discarded due to new blocks: 0
[2013-11-25 01:24:24] Unable to get work from server occasions: 0
[2013-11-25 01:24:24] Work items generated locally: 0
[2013-11-25 01:24:24] Submitting work remotely delay occasions: 10
[2013-11-25 01:24:24] New blocks detected on network: 70

[2013-11-25 01:24:24] Summary of per device statistics:

[2013-11-25 01:24:24] BAL0 | (5s):5.797G (avg):5.507Gh/s | A:40318 R:171 HW:273 WU:0.0/m
[2013-11-25 01:24:24]

[eleuthria]

Deepbit makes sense.  Their servers are outdated and still use getwork.  Don't waste your time trying to use an ASIC over getwork.


What's strange is BTC Guild output showing 27 GH/s.  I do see one work submit delay, which could have been a disconnect/loss of connection on 3G.  The hardware errors seem a little high, but I'm not too familiar with BFL ASICs.  Your reject rate looks sane for BFL + 3G (higher latency) connection.

I'm actually wondering if you've been given a 25 GH/s mini-single instead of a 50 GH/s full single.

[Photon939]

Looks to me like you either got a Little single or there was a hardware malfunction with your single. BFG/CGminer base the device type on the number of working chips reported by the Atmel microprocessor inside. BAL = BFL ASIC Little Single, BAS = BFL ASIC Single

See if you can shine a flashlight into the vents or take the cover off; if you see two heatsinks inside then it is indeed a full single. If you only see one big heatsink it's a little single.

[vm1990]

im going to say its due to the 3g connection. i tried it in the UK and struggled alot at getting gull speed. operators have a heavy limit of 3g connection and while mining dosnt require alot of bandwidth its constantly sending and receiving data which the automated system dosnt like

[eleuthria]

im going to say its due to the 3g connection. i tried it in the UK and struggled alot at getting gull speed. operators have a heavy limit of 3g connection and while mining dosnt require alot of bandwidth its constantly sending and receiving data which the automated system dosnt like

3G will not impact mining speed, especially locally reported speed.  Mining over stratum protocols (which Guild uses) can be done even on a 56K.  It uses less than 0.1 KB/s.

[-ck]

Cgminer is recognising it as a little single. Either a board's completely offline/dead or it isn't populated at all as Photon939 said.

[vm1990]

im going to say its due to the 3g connection. i tried it in the UK and struggled alot at getting gull speed. operators have a heavy limit of 3g connection and while mining dosnt require alot of bandwidth its constantly sending and receiving data which the automated system dosnt like

3G will not impact mining speed, especially locally reported speed.  Mining over stratum protocols (which Guild uses) can be done even on a 56K.  It uses less than 0.1 KB/s.

it might not affect it locally but will affect it on the pool side
1. 3g is not as stable as a line connection
2. 3g can suffer huge ping spikes for long rime periods which does matter when mining
3. dial up atleast is stable and not affected by weather and other users