hmm, I don't know what run_p2pool.exe is but CGMiner supports the new standard of the stratum protocol which you'll find many many pools support.
i boot off of a USB stick which I prefer to do as little as possible with. Maintaining a single binary for me is the easiest.
Topic: CGMiner variance? (Read 456 times)
Wow, thanks MonkeyMonkey. Looking at Eligius, it looks promising also. With P2Pool, I had to download run_p2pool.exe, but Eligius says just to use CGMiner. Does it not require another executable to run in conjunction with the miner? Is that just a p2pool thing? Sorry, obviously I'm new trying to learn all I can! Thanks again!
some of it could also depend on pool.
I find that my short term reported hash rate fluctuates by as much as +/-20% at the pool vs. what CGMiner reports in the short term but evens out to pretty close over the long term.
i use http://eligius.st/
I find that my short term reported hash rate fluctuates by as much as +/-20% at the pool vs. what CGMiner reports in the short term but evens out to pretty close over the long term.
i use http://eligius.st/
Thank you very much Lucky! It makes sense now!
I don't know about P2Pool, but on the bitcoipool.com FAQ, they have this to say...
Q: My hashing speed (mhash/sec) is different on the server and on my miner?
We view all the shares that were submitted in a 5 minute window (from 5 minutes ago to now), multiply by 2^32 (the size of a getwork) and then divide by the number of seconds in 5 minutes. Then divide by 1000 three times to make Gh/s. It's fairly accurate. Obviously you'll see inflated speeds if you submit more than one share per requested getwork, and the reverse is true as well. It's estimated. As there is no way for us to query the client itself, we have to guess, and this is the closest way to guess.
I've noticed that my hash speed on the pool is ussualy about half of what my cg or bfg miner says it is running at.
Q: My hashing speed (mhash/sec) is different on the server and on my miner?
We view all the shares that were submitted in a 5 minute window (from 5 minutes ago to now), multiply by 2^32 (the size of a getwork) and then divide by the number of seconds in 5 minutes. Then divide by 1000 three times to make Gh/s. It's fairly accurate. Obviously you'll see inflated speeds if you submit more than one share per requested getwork, and the reverse is true as well. It's estimated. As there is no way for us to query the client itself, we have to guess, and this is the closest way to guess.
I've noticed that my hash speed on the pool is ussualy about half of what my cg or bfg miner says it is running at.
Greetings all, I have another noobish question.
I'm using CGMiner 3.1.1 and P2Pool 11.4.
The CGMiner shows a hashrate of around 160mh/s, and the P2Pool console window is showing around 143mh/s. When I go to http://127.0.0.1:9332/static/, and look at the stats, it is often showing a much lower rate, something around 100mh/s. Sometimes the numbers do match up, but most of the time there is a discrepancy. Is this a problem? That is to say, am I really running at only 100mh/s, is this somehow misreported on the stats report, or is this accurate, and the reflection of some type of lag between the miner, p2pool, and the stats page?
Thanks again for all your help.. this has been the only place I've been able to find with accurate info!
I'm using CGMiner 3.1.1 and P2Pool 11.4.
The CGMiner shows a hashrate of around 160mh/s, and the P2Pool console window is showing around 143mh/s. When I go to http://127.0.0.1:9332/static/, and look at the stats, it is often showing a much lower rate, something around 100mh/s. Sometimes the numbers do match up, but most of the time there is a discrepancy. Is this a problem? That is to say, am I really running at only 100mh/s, is this somehow misreported on the stats report, or is this accurate, and the reflection of some type of lag between the miner, p2pool, and the stats page?
Thanks again for all your help.. this has been the only place I've been able to find with accurate info!
Jump to: