Bitcoin Forum
November 03, 2024, 11:14:19 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Blade Block Erupter spends a lot of time asking for work w/o doing much...  (Read 1028 times)
jfarr245 (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
September 30, 2013, 02:28:22 PM
 #1

Hi!

My 10GH/s Block Erupter Blade is configured to mine on Bitminter.com.  I use mining_proxy.exe on my computer to act as a proxy between the blade & the site.  I watch the "command prompt window' on the server and it seems to send more lines asking for work than submitting results.  Is there any way to increase it's work output w/o overclocking?

One thing that concerns me is that the unit is producing 0.015xxx to 0.02xxx BTC/day.  According to calculators, it should be earning ~.03 BTC/day.  I know it isn't a huge difference, but I would like to get as much as I can out of it.

Details from Block Erupter...

Total MHS:   10823
Received:   0000091087
Accepted:   0000089784
Per Minute:   147.82
Efficiency:   098.57%
Up Time:   0d,10h,07m,22s  (It was up for over 7 days before I reset it last night...)

Command on server...

c:\mining_proxy.exe -o mint.bitminter.exe -sp 3333 -gp 8332

I have a good cable internet connection.

Any pointers would be appreciated!
vm1990
Legendary
*
Offline Offline

Activity: 1540
Merit: 1002



View Profile
October 02, 2013, 12:05:15 AM
 #2

iv not played with it but on the proxy try loosing the -gp 8332 bit dont think bitminter supports it anyway


HellDiverUK
Hero Member
*****
Offline Offline

Activity: 1246
Merit: 501



View Profile
October 02, 2013, 07:55:58 AM
 #3


My 10GH/s Block Erupter Blade is configured to mine on Bitminter.com.  I use mining_proxy.exe on my computer to act as a proxy between the blade & the site.  I watch the "command prompt window' on the server and it seems to send more lines asking for work than submitting results.  Is there any way to increase it's work output w/o overclocking?


Normal behavior.

The Blade asking for new work is normal, the proxy generates getwork work itself, so the Blade must ask for new work. Basically the Blade is saying  "I'm finished, next please". 

iv not played with it but on the proxy try loosing the -gp 8332 bit dont think bitminter supports it anyway

Useless advice.  All -gp 8332 does is set the getwork port on the proxy to 8332.   Next time you're going to give advice, try finding out what you're talking about first.  Roll Eyes
matt4054
Legendary
*
Offline Offline

Activity: 1946
Merit: 1035



View Profile
October 02, 2013, 08:07:07 AM
 #4

AFAIK, BitMinter stratum uses variable difficulty. On the other hand, the Blade only supports difficulty 1 getwork. It means that if stratum is requesting diff 8 shares, only 1/8 of the work will actually ever get returned (and accepted), and it is expected behaviour. It shouldn't affect your mining revenues in the long run.

Since BitMinter is PPLNS, your revenue is also influenced by pool luck. I have one blade hashing since last May, previously it was on BitMinter too but I switched to a PPS pool about 2 month ago now.
jfarr245 (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
October 02, 2013, 02:47:51 PM
 #5

Thanks for the advice!  It makes me feel better to know that the device is doing what it is supposed to do!  Smiley  It is my first attempt at ASIC mining & I was unsure if I had it setup correctly.

Is there much/any difference between PPS/PPLS (sorry if I screwed that up...was going from memory)?  I did some reading & the idea that I came up with was that there is not much difference overall.

Also,  is there a "better" pool to mine with?  I use bitminter, but have heard good things about others b/c they are bigger.  Again,  I've read that it doesn't really matter in the end.  But I'd really value the advice of those who do it & know a lot more than I.

Thanks for your advice!

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!