Bitcoin Forum
November 10, 2024, 02:20:01 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Mini rig and connectivity issue  (Read 926 times)
papamoi (OP)
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250


View Profile
April 10, 2013, 08:48:14 PM
 #1

hi guys,

i have a technical question,

i have one friend who have set up a mini rig on some servers and he claims to have around 1000 gigahash/sec minimum.and he is doing solomining on it but the issue is that the btc generated are very little ,around 15/20 btc a day, i do not know how is he able to generate this btc with without getting any entire block but the thing is that he is claiming that the btc is generated is lower because sometimes he is not getting any information from the network and the hashrate is coming to 0.

so my question is what should he do to make generate the estimate number generated in poolmining with the same rate?

if anybody can help in this,that would be great

thank you guys
Marrs
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
April 10, 2013, 09:27:51 PM
 #2

1000 GH/s is the speed of 15 Avalons. If they were solo mining, you would theoretically expect 65 or so BTC per day, on average.

When you solo mine, you get 25 BTC (plus transaction fees) if you solve the block, and you get nothing if you don't.

That means it's not possible to solo mine and earn an amount that is not close to some multiple of 25.

Sounds like your friend is lying to you.



papamoi (OP)
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250


View Profile
April 10, 2013, 10:51:38 PM
Last edit: April 10, 2013, 11:17:53 PM by papamoi
 #3

1000 GH/s is the speed of 15 Avalons. If they were solo mining, you would theoretically expect 65 or so BTC per day, on average.

When you solo mine, you get 25 BTC (plus transaction fees) if you solve the block, and you get nothing if you don't.

That means it's not possible to solo mine and earn an amount that is not close to some multiple of 25.

Sounds like your friend is lying to you.





ok thanks for the replies this is what i thought

so do you think there is something wrong here ?
do you think what he said about connectivity issues etc is possible?
 
StringTheory
Member
**
Offline Offline

Activity: 69
Merit: 10


Making Sense of Things


View Profile
April 11, 2013, 12:06:04 AM
 #4

He just told you how that is not possible.  It needs to be close to a multiple of 25 because he has to earn and entire block on his own to earn anything significant.  He is probably not telling you the truth, the whole truth, and certainly something other than the truth.

Successful Transactions: jayson3 +1
papamoi (OP)
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250


View Profile
April 11, 2013, 01:03:08 AM
 #5

He just told you how that is not possible.  It needs to be close to a multiple of 25 because he has to earn and entire block on his own to earn anything significant.  He is probably not telling you the truth, the whole truth, and certainly something other than the truth.

i ve got the block point,and i knew this was a lie.

now as this guys seems like an overclock server expert,i want to verifiy about the networking issues he seems to get.

so i m trying to understand if there is any truth on this ,or is this another lie?

thank you for helping guys

fpgaminer
Hero Member
*****
Offline Offline

Activity: 560
Merit: 517



View Profile WWW
April 11, 2013, 01:54:12 AM
Last edit: April 11, 2013, 09:25:35 AM by fpgaminer
 #6

Running any high performance bitcoin mining operation will run into networking issues.  The traditional method of getting mining work to a machine is the getwork protocol, which will provide ~4 billion hashes worth of work per request. (Of course extensions to the getwork protocol improve this).  A single 3 module Avalon machine will churn through that work in ~0.07 seconds.  In other words, a single Avalon machine would need to make 13 getwork requests per second.  getwork requests are expensive, and thus put a large strain not only on the network connection, but also the server providing the work.  Also note that, on average, for every getwork request, there will be a corresponding submission of shares.

Extensions to the getwork protocol, getblocktemplate, or the stratum protocol can all be used to alleviate these problems and are mandatory for any modern mining setup for the reason illustrated above.

So, that covers the networking issues.  However, the source of your mining work must also be considered.  Hypothetically, if someone did have a 1TH/s mining farm, they would be foolish to mine at a pool with it.  The pools will not handle that load well, and will constantly fail to fulfill the needs of such a mining farm.  The better option would be mining solo by setting up your own private pool.  Second to that would be a local mining proxy that distributes the work load to multiple pools.

papamoi (OP)
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250


View Profile
April 11, 2013, 08:22:56 AM
 #7

thanks for your replies fgpa miner

it helps

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!