Quote from: Handofmidas on December 29, 2014, 11:09:32 AM

Quote from: sp_ on December 21, 2014, 10:05:34 PM

Quote from: Handofmidas on December 21, 2014, 05:52:44 PM

Good job as always SP! Lyra2 hash is a bit better.

However, same issue as with x11: Pool does not report the full hashrate. I think this is a ccminer 1.5.x related problem. For the original ccminer-Lyra2RE, pools show the correct hashrate as it is displayed in the miner. Would you mind to include the Lyra2 improvements into djm34's ccminer-Lyra2RE release?

I have done some fixes in x11 , is it still underrepporting in release 21?

Lyra is currently only finding one solution and the throughput is big. I will add 2 solutions soon.

I am considering to change the fork to the DJM34 fork. Clean it and replace all the kernals.

1. Less crashes.
2. Fix the problem on some pools.

But will lack some features like the API etc..

Hi, hope you guys had a good Christmas! As promised earlier, I have tested X11 with release21, and the hashrate is still not fully recognized by (some?) pools. Here's the graph for 16h of mining.

from what i can gather with all the mining thats been done - there is NO pool that will give a totally accurate hashrate ...

this is due to the collation of the previous accepted shares and the hashrate is calculated on THOSE accepted shares only for the period of time that the pool takes the sample shares ... most pools take this period of time to be 10 minutes - but some longer ...

this means that no matter what the miner itself says its doing - the pool will not show the same ...

this is why we can only get an _estimate_ of what the hashrate may be from the pools - and a more _accurate estimate_ from the miner itself ...

the hashrates from the miner are usually around the same figure - with a small splay percentage ...

the hashrates from the pools are usually much more splayed and have a higher degree of variance ...

result? ... the most accurate representation of hashrate is from the miner itself ...

thats my take on it anyway ... can anyone shed more light on this situation? ...

#crysx