Bitcoin Forum
December 11, 2016, 12:18:33 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Is it possible to get an accruate Mhash rate based on number of shares  (Read 1665 times)
Xenland
Legendary
*
Offline Offline

Activity: 980


I'm not just any shaman, I'm a Sha256man


View Profile
June 08, 2011, 12:49:18 AM
 #1

Believe me when I tell you, I know it sounds like a stupid question but seriously is it possible to get an accurate Mhash rate based on the share data pushpoold submits?
All my formulas come out accurate at first but once there its more or less workers they go off the charts in accurate!
I've seen other pooling services make this mistake of inaccuate hashing scores mine are usually at a ~20 Mhash/s error rate, which might piss some
new combing miners off when they come to find that they "Might" be making less Mhashes then their minors are reporting.

So is it possible to get an accruate mhash rate with the following data per share submitted
Fields:
id | timestamp | username

This is the last formula I attempted to use

Most recent share  submitted in time stamp
Minus(-)
First share submitted in round time stamp
Equals = Total Time Connected

TotalTimeConnected
Divided By(/)
Total Shares Subbmitted this round
Equals = Failed horribly at accurate Mhash Rate.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481458713
Hero Member
*
Offline Offline

Posts: 1481458713

View Profile Personal Message (Offline)

Ignore
1481458713
Reply with quote  #2

1481458713
Report to moderator
redhatzero
Full Member
***
Offline Offline

Activity: 126



View Profile
June 08, 2011, 02:20:05 AM
 #2

I'm using s.th. Like this (got some hints in the Pushpool thread):

NrOfShares / timeframe * 4294967296

That should be hashes per second if pushpool is rewriting difficulty to 1

But due to the nature of shares, I wouldn't call that accurate. It will always be more like a guess


Xenland
Legendary
*
Offline Offline

Activity: 980


I'm not just any shaman, I'm a Sha256man


View Profile
June 08, 2011, 02:37:26 AM
 #3

I'm using s.th. Like this (got some hints in the Pushpool thread):

NrOfShares / timeframe * 4294967296

That should be hashes per second if pushpool is rewriting difficulty to 1

But due to the nature of shares, I wouldn't call that accurate. It will always be more like a guess



Is this the current difficulty?
4294967296
PwrLeveld
Member
**
Offline Offline

Activity: 84



View Profile
June 08, 2011, 02:43:14 AM
 #4

No, I don't beleive so. However, I do not know the current dificulty but it says it in the wiki.
redhatzero
Full Member
***
Offline Offline

Activity: 126



View Profile
June 08, 2011, 02:49:17 AM
 #5

No, it's 2^32 which should be the whole keyspace for one workpacket if I remember right

http://forum.bitcoin.org/index.php?topic=8707.msg137869#msg137869

M2Ys4U
Newbie
*
Offline Offline

Activity: 6


View Profile
June 08, 2011, 04:42:14 AM
 #6

Hashes per second = Number of shares * 2^32 / time delta

Where time delta is the number of seconds you're reporting the hashrate average over.
Xenland
Legendary
*
Offline Offline

Activity: 980


I'm not just any shaman, I'm a Sha256man


View Profile
June 08, 2011, 08:43:36 AM
 #7

So i used this formula and i got 8 hashes per second?

Update: I figured out i did the formula backwards but its still not even close?

$hashesPerSecond =  $numShares / $fiveMinutesAgo * 4294967296;
The result is 16.345 Hahses/s
but my miner runs as 85000 Khash/s

UPDATE: I was using $fiveminutesago, and not the amount of time that has passed
M2Ys4U
Newbie
*
Offline Offline

Activity: 6


View Profile
June 09, 2011, 01:01:01 AM
 #8

It will vary wildly. Using that formula, a 600 second time delta and approx 66MHash/s I get reports between 20MHash/s and 120MHash/s, but that's just statistical variance.
Xenland
Legendary
*
Offline Offline

Activity: 980


I'm not just any shaman, I'm a Sha256man


View Profile
June 09, 2011, 02:34:09 AM
 #9

It almost seems like we should use a Minutes Per Share graph instead of an Mhash graph since they are so unpredictably inaccurate.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!