Topic: hashkill - testing bitcoin miner plugin - page 12. (Read 90959 times)
I'm a proud owner of a system with dual 6990s and the problem that I'm having with hashkill is that my queue keeps running dry. I understand that there is a work around (by spawning multiple hashkill instances), but has there been any progress in keeping the queue saturated? I think that this would be the single biggest improvement for me (considering that I've upgraded to dual PSUs so I'm thinking about about getting a 3rd 6990 for my system), which would make me extremely happy and warrant a donation...
gat3way --
Are you still developing this plugin (optimizing, adding features, etc.)?
In the last day or so, I've been getting this A LOT
[error] (ocl_bitcoin.c:239) Long polling failure, will retry in 20s!
Moreover, I'm getting
Speed: 283 MHash/sec [cur: 63%] [proc: 147] [subm: 107] [stale: 8] [eff: 72%]
(I'm using deepbit.net)
Which looks like a bit high on the stale shares -- possibly because long polling isn't working?
What do you think it might be?
Are you still developing this plugin (optimizing, adding features, etc.)?
In the last day or so, I've been getting this A LOT
[error] (ocl_bitcoin.c:239) Long polling failure, will retry in 20s!
Moreover, I'm getting
Speed: 283 MHash/sec [cur: 63%] [proc: 147] [subm: 107] [stale: 8] [eff: 72%]
(I'm using deepbit.net)
Which looks like a bit high on the stale shares -- possibly because long polling isn't working?
What do you think it might be?
Heat is a bitch. But then, it could be much worse - there are places much warmer than Bulgaria. And electricity is cheap ATM (however with that renewable energy EU crap it might soon get much more expensive).
The only problem i have is heat. And summer is also going to take it's toll. But no matter how i look at it, a 6950 uses about 160w at stock and does ~310 Mhash/s.
Pooled.
BTW, I've put an estimations table (for hashkill, but ratios should be OK for other miners though speeds won't be the same):
http://www.gat3way.eu/est.php
It is surprisingly accurate eheh, real speeds vary up to +/- 1.5% as compared to estimations on real tests I've done on different hardware. Formula is rather simple, but anyway we are getting OT here...
So I guess 5850 is more energy efficient than 6950. But then other factors come into play (e.g you may be limited on pcie slots or stuff, then faster cards may be better even if they are not that power-efficient).
BTW, I've put an estimations table (for hashkill, but ratios should be OK for other miners though speeds won't be the same):
http://www.gat3way.eu/est.php
It is surprisingly accurate eheh, real speeds vary up to +/- 1.5% as compared to estimations on real tests I've done on different hardware. Formula is rather simple, but anyway we are getting OT here...
So I guess 5850 is more energy efficient than 6950. But then other factors come into play (e.g you may be limited on pcie slots or stuff, then faster cards may be better even if they are not that power-efficient).
Are you solo gat3? I was thinking of getting another 5850 so i can CF, however a 6950 is not a bad choice either(minus the CF).
Should still be profitable considering EVN charges 0.18BGN for 1KW
Should still be profitable considering EVN charges 0.18BGN for 1KW
Shouldn't slow down. File is rather small. It is overwritten each 5 seconds so if you want to generate graphs or stuff, you gotta write a script that parses that each 5 secs and e.g updates a sql database. hashkill does not keep history of past values.
P.S if you need to tune speed, play with -D and -G2/-G3/-G4 options until you find a balance. -D -G2 works best for me (2x5870/1x6870).
P.S if you need to tune speed, play with -D and -G2/-G3/-G4 options until you find a balance. -D -G2 works best for me (2x5870/1x6870).
I got it now. Thanks.
BTW is it possible to turn off the writing logfile info to disk? Does it slow things down at all?
BTW is it possible to turn off the writing logfile info to disk? Does it slow things down at all?
Hm, browser caching issues?
The date on the executable is 5/11/2011
Also, I don't see a folder in my home directory named ".hashkill"
Did I download the new version before you updated the .tgz?
Also, I don't see a folder in my home directory named ".hashkill"
Did I download the new version before you updated the .tgz?
Ехех безсъние 
Що не спиш бре gat3way 
Nice release though.
Nice release though.
A new version, this time beta quality.
Fixed:
* progress indicator issues (sigh)
* better queueing mechanism
* ADL thermal monitoring stuff now works correctly - you should have thermal monitoring and stats for all your GPUs
* fixed bug on some systems causing hashkill to stop properly submitting shares
* improved multi-gpu support
* mining.bitcoin.cz now properly reports account info when -a is used with the correct API key
New feature:
* progress now autosaved in a text file, json format. It is autosaved in ~/.hashkill/bitcoin.json . This file can be parsed in order to implement external tools that collect statistics, draw graphs, provide web interface and stuff. This feature will be extended in the future to provide GPU temps info and pool stats.
Download:
64-bit:
http://www.gat3way.eu/poc/hashkill-0.2.4-x86_64.tgz
32-bit:
http://www.gat3way.eu/poc/hashkill-0.2.4-x86.tgz
Please use sudo ./install.sh or run install.sh as root. This is especially important if you have previously installed hashkill - older files need to be overwritten.
Fixed:
* progress indicator issues (sigh)
* better queueing mechanism
* ADL thermal monitoring stuff now works correctly - you should have thermal monitoring and stats for all your GPUs
* fixed bug on some systems causing hashkill to stop properly submitting shares
* improved multi-gpu support
* mining.bitcoin.cz now properly reports account info when -a is used with the correct API key
New feature:
* progress now autosaved in a text file, json format. It is autosaved in ~/.hashkill/bitcoin.json . This file can be parsed in order to implement external tools that collect statistics, draw graphs, provide web interface and stuff. This feature will be extended in the future to provide GPU temps info and pool stats.
Download:
64-bit:
http://www.gat3way.eu/poc/hashkill-0.2.4-x86_64.tgz
32-bit:
http://www.gat3way.eu/poc/hashkill-0.2.4-x86.tgz
Please use sudo ./install.sh or run install.sh as root. This is especially important if you have previously installed hashkill - older files need to be overwritten.
Site is down 
Anybody have a copy? Torrent file?
Anybody have a copy? Torrent file?
check PM...
Site is down
Anybody have a copy? Torrent file?
Anybody have a copy? Torrent file?
Well,I know this sucks, but I am too tired of that "release early, release often" stuff. I need some more time to properly address all the issues instead of relying on feedback for each small incremental improvement and bugfix.
No as it is a 64bit ubuntu it should be using the 64 bit version (or is this a flag or something which must be set explicitly)?
The sad thing is that ATM it is very hard to compare hash speed with other miners as you have to rely on the rates reported by the pool (which tend to jump up and down around 100mhash).
Looking forward to your next release!
The sad thing is that ATM it is very hard to compare hash speed with other miners as you have to rely on the rates reported by the pool (which tend to jump up and down around 100mhash).
Looking forward to your next release!
I am aware of that bug (you are using the 32-bit version I suppose?).
There are also issues with the ADL monitoring I am currently working on.
And since I am building a small rig as well, I noticed some things that can be improved. For example we can log the output into a convinient to parse file or SQL database so that web frontend can be done much less painfully. So there is some work to do. I will hopefully release a new version in 2 or 3 weeks. No performance benefits expected though
There are also issues with the ADL monitoring I am currently working on.
And since I am building a small rig as well, I noticed some things that can be improved. For example we can log the output into a convinient to parse file or SQL database so that web frontend can be done much less painfully. So there is some work to do. I will hopefully release a new version in 2 or 3 weeks. No performance benefits expected though
Just testing hashkill with ubuntu 11.4 and 3x5830 + 1x6870.
It seems to work fine (aticonfig --odgc shows 99% usage), and also the pool website shows around the speed i am expecting (900-1000 mhash/s).
However hashkill itself only shows between 110 and 140 mhash..
Any idea whats wrong? Do you need any further logs?
It seems to work fine (aticonfig --odgc shows 99% usage), and also the pool website shows around the speed i am expecting (900-1000 mhash/s).
However hashkill itself only shows between 110 and 140 mhash..
Any idea whats wrong? Do you need any further logs?
Quote
How can this be possible...?
And anyway why there is difference between processed and submitted?
And anyway why there is difference between processed and submitted?
It is possible because you can have either 0, or 1 or more than 1 possible "solutions" for a single getwork.
Quote
What is "abnormally high"?
It would be very useful to know the number of "real" stale shares and the invalid ones to diagnose hw problems.
For example, I've an efficiency of around only 90%: is this an "abnormally low" number?
(I suspect it should be near 100%)
It would be very useful to know the number of "real" stale shares and the invalid ones to diagnose hw problems.
For example, I've an efficiency of around only 90%: is this an "abnormally low" number?
(I suspect it should be near 100%)
Without -D I guess anything below 3% would be OK, with -D probably more. Stale percentage of 20 for example smells rather fishy.
Jump to: