Jump to content

Not sure how often this gets asked, but why does my miner report a constant hashrate but the pool reports a drastically variable hashrate?  It's on a computer that isn't used at all, just remoted into every now and then.

 

My assumption is it depends on the shares you get vs shares that are partial?  I know F@H has a points system so some are worth more than others but isn't a share just a share on a pool?  I'm running kapow right now but it doesn't matter what coin I use or what miner I use.  Just looking for some insight.

Audio go Brrrrrr

Link to comment
https://linustechtips.com/topic/1346948-constant-rate-reported-different/
Share on other sites

Link to post
Share on other sites

I don't have a ton of experience with mining pools, but as far as I know your description is kinda backwards. You don't have a share of a fixed pool; rather, the pool is the sum of all of its users' individual hashrates. Your individual hashrate doesn't change much, but as users join and leave the pool, its total hashrate changes.

Link to post
Share on other sites

3 hours ago, Grabhanem said:

I don't have a ton of experience with mining pools, but as far as I know your description is kinda backwards. You don't have a share of a fixed pool; rather, the pool is the sum of all of its users' individual hashrates. Your individual hashrate doesn't change much, but as users join and leave the pool, its total hashrate changes.

My point is that my current reported and average hashrate is not consistent.  My miner hashrate reads dead on balls constant.  What is the discrepancy? 

Audio go Brrrrrr

Link to post
Share on other sites

8 hours ago, Psittac said:

My point is that my current reported and average hashrate is not consistent.  My miner hashrate reads dead on balls constant.  What is the discrepancy? 

Current and average hashrate generally aren't the same in my experience. Even more so if you compare local to online. The current reported hashrate is what it's currently doing. The average one is averaged over some timespan.

 

The discrepancy between the two I think is most likely that the miner itself is reporting raw hashrate. If you take a long time to submit or receive stuff to or from the pool, however, you'll have a lower effective hashrate.

Crystal: CPU: i7 7700K | Motherboard: Asus ROG Strix Z270F | RAM: GSkill 16 GB@3200MHz | GPU: Nvidia GTX 1080 Ti FE | Case: Corsair Crystal 570X (black) | PSU: EVGA Supernova G2 1000W | Monitor: Asus VG248QE 24"

Laptop: Dell XPS 13 9370 | CPU: i5 10510U | RAM: 16 GB

Server: CPU: i5 4690k | RAM: 16 GB | Case: Corsair Graphite 760T White | Storage: 19 TB

Link to post
Share on other sites

  • 2 weeks later...

from what i understand reported hashrate is what your miner reports to the pool. current hash rate is an average calculated by the amount of effective shares your miners submits. from what i understand many people are trying to hash the same job but only one miner will complete the algo and find the correct answer. this is where a share is submitted. obviously with more hash power you can accept more jobs so in turn you have a greater chance of finding correct answers. i would look more at the average hash rate as that takes the average of submitted shares over a much longer period of time i think 6 hours or so. as long as your average is around the same as your reported hashrate you should be fine. 

 

hashrate.jpg.792d83a652cf09f693f233d7c170b5da.jpg

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×