Topic: DiabloMiner GPU Miner - page 59. (Read 866596 times)

Quote from: GODLIKE on June 02, 2011, 04:06:36 PM

After testing various parameters, I found a way to get 2mhash/s more out of diablo compared to phatk. Great! Grin

However, for the last 5 hours, deepbit never calculated a hashrate for me that was even close to the 270mhash/s shown by diablo. It was mostly ~150mhash/s, sometimes as "high" as 200mhash/s. (Using a 45 min average) (also, 1.65% stale shares - might be caused by deepbit though, not sure if long polling works 100% again)

Is it possible that certain parameters cause diablo to display a much higher hashrate than actually achieved (for example because some of the calculations fail silently), or is this just very bad luck?

I am seeing this same effect on other pools. I am also wondering if Diablo's hashrate calculations are wrong.

Nope, my hashrate is 100% correct. The problem is, OTHER miners do NOT look for OpenCL execution errors and happily count the hashes on a failed run.

If your Intenret is lagging badly, all miners, not just mine, will have strange hashrate drops because its blocking on share submission.

If you think there is actually a problem, compare vs a local running bitcoind.... if it STILL has large variations in hashrate, then there is an issue.

In addition to that, less than -f 15 often causes the OS clock to get jerky up to the point that the 15 second average (the first number) becomes very unreliable. In these situations, use the forever average only (the second number)... it usually becomes reliable within a minute or two.

Other miners suffer from this, but try various ways of covering it up; none are as accurate as using the forever average on mine over long periods.

I am seeing nearly double the found hashes with phoenix/phatk. None of them are being rejected by the pool. The hashrate being reported by the miners is nearly identical.

If the pool allocates shares based on submitted POWs and doesn't reject them, wouldn't I want the miner that submits more POWs over a given time period?

Are you sure you're using the absolute newest version of my miner? mtrlt's 0.5% speed increase accidentally had a bug that would cause similar behavior to half of shares missing. I fixed it shortly afterwards.

A dead giveaway of the bug is using -dd and seeing a ton of hardware check errors.

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

I tried as you say, this is the result:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Marco>cd C:\Users\Marco\Desktop\trunks\btc\DiabloMiner

C:\Users\Marco\Desktop\trunks\btc\DiabloMiner>C:\Users\Marco\Desktop\trunks\btc\
DiabloMiner\DiabloMiner-Windows.exe -u [email protected] -p XXX -o pit
.deepbit.net -r 8332
[02/06/11 23:04:47] Started
[02/06/11 23:04:47] Connecting to: http://pit.deepbit.net:8332/
Exception in thread "main" org.lwjgl.LWJGLException: Could not locate OpenCL lib
rary.
at org.lwjgl.opencl.CL.create(CL.java:121)
at com.diablominer.DiabloMiner.DiabloMiner.execute(DiabloMiner.java:379)

at com.diablominer.DiabloMiner.DiabloMiner.main(DiabloMiner.java:127)

C:\Users\Marco\Desktop\trunks\btc\DiabloMiner>

Either you do not have OpenCL drivers installed, or your device does not support OpenCL.

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Quote from: gentakin on June 02, 2011, 02:53:05 PM

After testing various parameters, I found a way to get 2mhash/s more out of diablo compared to phatk. Great! Grin

However, for the last 5 hours, deepbit never calculated a hashrate for me that was even close to the 270mhash/s shown by diablo. It was mostly ~150mhash/s, sometimes as "high" as 200mhash/s. (Using a 45 min average) (also, 1.65% stale shares - might be caused by deepbit though, not sure if long polling works 100% again)

Is it possible that certain parameters cause diablo to display a much higher hashrate than actually achieved (for example because some of the calculations fail silently), or is this just very bad luck?

I am seeing this same effect on other pools. I am also wondering if Diablo's hashrate calculations are wrong.

Trust me, my hashrate calculation is correct. If anything, poclbm is somewhat inaccurate and phoenix has been proven to be very inaccurate.

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Thanks for your fast reply!

If your Intenret is lagging badly, all miners, not just mine, will have strange hashrate drops because its blocking on share submission.

This seems to be no problem for me. I stopped diablo and fired up phoenix, and after some time the hashrate shown at deepbit's web site shows ~270mhash/sec, like I expected. I'm not having any connection issues, only my router sometimes stops working.
Is there a console output I should be watching for in diablo to see if it is taking a long time to submit shares? Both hash meters (total and 15sec average) showed 270mhash/s. (And why not submit shares in a seperate thread so there is no blocking?)

In addition to that, less than -f 15 often causes the OS clock to get jerky up to the point that the 15 second average (the first number) becomes very unreliable. In these situations, use the forever average only (the second number)... it usually becomes reliable within a minute or two.

This seems to be no problem for me as well. I don't specify -f on the command line, so I guess it's using a default value. With diablo, there is pretty much no desktop lag for me (while phatk causes same lag). The gnome clock updates fine, so this should be fine.

Quote from: gentakin on June 02, 2011, 03:20:01 PM

Other miners suffer from this, but try various ways of covering it up; none are as accurate as using the forever average on mine over long periods.

As I said, the forever average looked okay.

It's still possible, due to the random nature of mining, that the relatively low number of submitted shares was bad luck. Or maybe there is a bug that only appears on some systems (i.e. my system) and possibly only with some configurations that causes diablo to
* calculate hashrate wrong OR
* sometimes not submit/recognize a share even if it is valid.

Wait, hold up. Theres your problem. Deepbit's hash meter is 100% inaccurate and is counting a rare random event, ie, share generation. Do not use Deepbit's hash meter as a measure of performance.

My miner tends to swing the randomness of share generation around harder (due to working on independent work in parallel), but otherwise has no effect on actual share generation.

Also, I may consider submitting shares in a separate thread in the future, however I already run 3 mining threads per GPU and this tends to eliminate usual network lag issues.

GODLIKE

hero member

Activity: 546

Merit: 500

LOL what you looking at?

I tried as you say, this is the result:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Marco>cd C:\Users\Marco\Desktop\trunks\btc\DiabloMiner

C:\Users\Marco\Desktop\trunks\btc\DiabloMiner>C:\Users\Marco\Desktop\trunks\btc\
DiabloMiner\DiabloMiner-Windows.exe -u [email protected] -p XXX -o pit
.deepbit.net -r 8332
[02/06/11 23:04:47] Started
[02/06/11 23:04:47] Connecting to: http://pit.deepbit.net:8332/
Exception in thread "main" org.lwjgl.LWJGLException: Could not locate OpenCL lib
rary.
at org.lwjgl.opencl.CL.create(CL.java:121)
at com.diablominer.DiabloMiner.DiabloMiner.execute(DiabloMiner.java:379)

at com.diablominer.DiabloMiner.DiabloMiner.main(DiabloMiner.java:127)

C:\Users\Marco\Desktop\trunks\btc\DiabloMiner>

nyargh

newbie

Activity: 25

Merit: 0

it's a single 6870 from sapphire, using sdk 2.4, ubuntu 11.04 (I like unity, even though it might put some load on my gpu) and apt says my driver is "fglrx 2:8.840-0ubuntu4".
No manual over/underclocking.

Hmmm... I have a different setup, 2x sapphire 5830s, 2.4 SDK, 11.5 driver, debian squeeze. My cards are overclocked to the default bios max (875 mhz). This may be a more serious bug if it's affecting two very different setups. The only common thread here is the SDK and the platform (kinda).

gentakin

member

Activity: 98

Merit: 10

Quote from: nyargh on June 02, 2011, 03:11:26 PM

This is what I would suspect, but who knows? I am convinced that there is a bug in DiabloMiner. What is your setup? card / driver / sdk / os?

it's a single 6870 from sapphire, using sdk 2.4, ubuntu 11.04 (I like unity, even though it might put some load on my gpu) and apt says my driver is "fglrx 2:8.840-0ubuntu4".
No manual over/underclocking.

nyargh

newbie

Activity: 25

Merit: 0

Quote from: gentakin on June 02, 2011, 02:53:05 PM

* sometimes not submit/recognize a share even if it is valid.

This is what I would suspect, but who knows? I am convinced that there is a bug in DiabloMiner. What is your setup? card / driver / sdk / os?

gentakin

member

Activity: 98

Merit: 10

Thanks for your fast reply!

If your Intenret is lagging badly, all miners, not just mine, will have strange hashrate drops because its blocking on share submission.

This seems to be no problem for me. I stopped diablo and fired up phoenix, and after some time the hashrate shown at deepbit's web site shows ~270mhash/sec, like I expected. I'm not having any connection issues, only my router sometimes stops working.
Is there a console output I should be watching for in diablo to see if it is taking a long time to submit shares? Both hash meters (total and 15sec average) showed 270mhash/s. (And why not submit shares in a seperate thread so there is no blocking?)

In addition to that, less than -f 15 often causes the OS clock to get jerky up to the point that the 15 second average (the first number) becomes very unreliable. In these situations, use the forever average only (the second number)... it usually becomes reliable within a minute or two.

This seems to be no problem for me as well. I don't specify -f on the command line, so I guess it's using a default value. With diablo, there is pretty much no desktop lag for me (while phatk causes same lag). The gnome clock updates fine, so this should be fine.

Other miners suffer from this, but try various ways of covering it up; none are as accurate as using the forever average on mine over long periods.

As I said, the forever average looked okay.

It's still possible, due to the random nature of mining, that the relatively low number of submitted shares was bad luck. Or maybe there is a bug that only appears on some systems (i.e. my system) and possibly only with some configurations that causes diablo to
* calculate hashrate wrong OR
* sometimes not submit/recognize a share even if it is valid.

nyargh

newbie

Activity: 25

Merit: 0

After testing various parameters, I found a way to get 2mhash/s more out of diablo compared to phatk. Great! Grin

However, for the last 5 hours, deepbit never calculated a hashrate for me that was even close to the 270mhash/s shown by diablo. It was mostly ~150mhash/s, sometimes as "high" as 200mhash/s. (Using a 45 min average) (also, 1.65% stale shares - might be caused by deepbit though, not sure if long polling works 100% again)

Is it possible that certain parameters cause diablo to display a much higher hashrate than actually achieved (for example because some of the calculations fail silently), or is this just very bad luck?

I am seeing this same effect on other pools. I am also wondering if Diablo's hashrate calculations are wrong.

Nope, my hashrate is 100% correct. The problem is, OTHER miners do NOT look for OpenCL execution errors and happily count the hashes on a failed run.

If your Intenret is lagging badly, all miners, not just mine, will have strange hashrate drops because its blocking on share submission.

If you think there is actually a problem, compare vs a local running bitcoind.... if it STILL has large variations in hashrate, then there is an issue.

In addition to that, less than -f 15 often causes the OS clock to get jerky up to the point that the 15 second average (the first number) becomes very unreliable. In these situations, use the forever average only (the second number)... it usually becomes reliable within a minute or two.

Other miners suffer from this, but try various ways of covering it up; none are as accurate as using the forever average on mine over long periods.

I am seeing nearly double the found hashes with phoenix/phatk. None of them are being rejected by the pool. The hashrate being reported by the miners is nearly identical.

If the pool allocates shares based on submitted POWs and doesn't reject them, wouldn't I want the miner that submits more POWs over a given time period?

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author