Bitcoin Forum
December 07, 2016, 04:26:20 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 [9] 10 11 12 13 14 15 16 17 18 19 20 21 »  All
  Print  
Author Topic: hashkill - testing bitcoin miner plugin  (Read 85503 times)
gat3way
Sr. Member
****
Offline Offline

Activity: 256


View Profile
May 17, 2011, 05:04:46 PM
 #161

cur % is the percentage of the keyspace of the current getwork already calculated and checked. You have ~ 4 billion possible nonces per getwork that need to be tried. 50% would mean that we are currently trying nonce ~ 2 billion.

subm is the number of successfully submitted shares. It might be higher, lower or equal to the number of processed getworks.

stale is not quite appropriate as it includes both stale and invalid shares. Under normal circumstances, there shouldn't be any invalid ones, however with higher temperatures and too much OC, it is possible that the hardware starts calculating hashes incorrectly. Abnormally high stale numbers mean that there are hardware problems.
1481127980
Hero Member
*
Offline Offline

Posts: 1481127980

View Profile Personal Message (Offline)

Ignore
1481127980
Reply with quote  #2

1481127980
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481127980
Hero Member
*
Offline Offline

Posts: 1481127980

View Profile Personal Message (Offline)

Ignore
1481127980
Reply with quote  #2

1481127980
Report to moderator
1481127980
Hero Member
*
Offline Offline

Posts: 1481127980

View Profile Personal Message (Offline)

Ignore
1481127980
Reply with quote  #2

1481127980
Report to moderator
Dusty
Hero Member
*****
Offline Offline

Activity: 722


Libertas a calumnia


View Profile WWW
May 17, 2011, 06:35:36 PM
 #162

Thank you gat3way for the explainations, I need some clarifications, though:
subm is the number of successfully submitted shares. It might be higher, lower or equal to the number of processed getworks.
How can this be possible...?
And anyway why there is difference between processed and submitted?

Quote
stale is not quite appropriate as it includes both stale and invalid shares. Under normal circumstances, there shouldn't be any invalid ones, however with higher temperatures and too much OC, it is possible that the hardware starts calculating hashes incorrectly. Abnormally high stale numbers mean that there are hardware problems.
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%)

Thanks in advance!

Articoli bitcoin: Il portico dipinto
gat3way
Sr. Member
****
Offline Offline

Activity: 256


View Profile
May 17, 2011, 07:40:56 PM
 #163

Quote
How can this be possible...?
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%)

Without -D I guess anything below 3% would be OK, with -D probably more. Stale percentage of 20 for example smells rather fishy.
leepfrog
Full Member
***
Offline Offline

Activity: 126

Hopity Hopity Hop


View Profile
May 23, 2011, 06:25:24 PM
 #164

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?

-----Crypto--Investor----Family--Guy-----All--Around--Winner----
gat3way
Sr. Member
****
Offline Offline

Activity: 256


View Profile
May 23, 2011, 07:54:37 PM
 #165

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
leepfrog
Full Member
***
Offline Offline

Activity: 126

Hopity Hopity Hop


View Profile
May 23, 2011, 08:07:33 PM
 #166

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!

-----Crypto--Investor----Family--Guy-----All--Around--Winner----
gat3way
Sr. Member
****
Offline Offline

Activity: 256


View Profile
May 23, 2011, 08:27:37 PM
 #167

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.
gigabytecoin
Sr. Member
****
Offline Offline

Activity: 280


View Profile
May 26, 2011, 07:46:32 AM
 #168

Site is down Sad

Anybody have a copy? Torrent file?
Jaime Frontero
Full Member
***
Offline Offline

Activity: 126


View Profile
May 26, 2011, 08:17:41 AM
 #169

Site is down Sad

Anybody have a copy? Torrent file?

check PM...
gat3way
Sr. Member
****
Offline Offline

Activity: 256


View Profile
May 27, 2011, 10:22:15 PM
 #170

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.
dikidera
Full Member
***
Offline Offline

Activity: 126


View Profile
May 27, 2011, 10:23:41 PM
 #171

Що не спиш бре gat3way   Grin

Nice release though.
gat3way
Sr. Member
****
Offline Offline

Activity: 256


View Profile
May 27, 2011, 10:43:44 PM
 #172

Ехех безсъние Smiley
AngelusWebDesign
Sr. Member
****
Offline Offline

Activity: 392


View Profile
May 27, 2011, 10:50:11 PM
 #173

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?
gat3way
Sr. Member
****
Offline Offline

Activity: 256


View Profile
May 27, 2011, 10:51:23 PM
 #174

Hm, browser caching issues?
AngelusWebDesign
Sr. Member
****
Offline Offline

Activity: 392


View Profile
May 27, 2011, 11:00:27 PM
 #175

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?
gat3way
Sr. Member
****
Offline Offline

Activity: 256


View Profile
May 27, 2011, 11:03:54 PM
 #176

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).
dikidera
Full Member
***
Offline Offline

Activity: 126


View Profile
May 27, 2011, 11:08:00 PM
 #177

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
gat3way
Sr. Member
****
Offline Offline

Activity: 256


View Profile
May 27, 2011, 11:11:13 PM
 #178

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).
dikidera
Full Member
***
Offline Offline

Activity: 126


View Profile
May 27, 2011, 11:16:17 PM
 #179

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.
gat3way
Sr. Member
****
Offline Offline

Activity: 256


View Profile
May 27, 2011, 11:22:24 PM
 #180

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).
Pages: « 1 2 3 4 5 6 7 8 [9] 10 11 12 13 14 15 16 17 18 19 20 21 »  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!