|
Keninishna
|
 |
June 30, 2011, 11:52:59 AM |
|
Here is my output:  Adding the -D option gave me about 5 mh/s extra  |
|
|
|
|
|
|
|
|
|
|
|
Transactions must be included in a block to be properly completed. When you send a transaction, it is broadcast to miners. Miners can then optionally include it in their next blocks. Miners will be more inclined to include your transaction if it has a higher transaction fee.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
gat3way (OP)
|
|
June 30, 2011, 09:22:31 PM |
|
Yeah and I can clearly see that "GPU drop" effect  Gotta be some synchronization bug, I will have a look at that... |
|
|
|
|
SkipDaShu
Newbie
 Offline
Activity: 27
Merit: 0
|
|
July 01, 2011, 02:22:59 AM |
|
Curious... haven't seen a compare between HashKill and the Diablo miner here.
|
|
|
|
|
|
gat3way (OP)
|
|
July 02, 2011, 09:23:56 PM |
|
OK think I found what causes that GPU drop. Also pool failover coming soon. I also found a small bug that potentially caused more stales under certain circumstances. Will release soon.
|
|
|
|
|
|
kripz
|
|
July 02, 2011, 11:37:44 PM |
|
Is your hasher optimised for the 5000 series? I seem to get get less hash rate (50+) and also less shares per hour.
|
|
|
|
|
gat3way (OP)
|
|
July 03, 2011, 10:19:35 AM |
|
Is your hasher optimised for the 5000 series? I seem to get get less hash rate (50+) and also less shares per hour.
As compared to what? |
|
|
|
|
|
gat3way (OP)
|
|
July 03, 2011, 10:25:00 AM |
|
OK, new release is here. What's new: * GPU drop problem should be fixed * Added pools stats for btcguild.com. Use -a <apikey> * Fixed a race condition situation which would submit more stale shares under certain circumstances * Added pool failover support. It is enabled by using the -f <inputfile> option. You create a text file in the following format: user:password:host:port user1:password1:host1:port1 ... then you run hashkill like this: hashkill -p bitcoin -f filename The end-result would be that once there are connection failures to a pool, we switch to the next one in the list. No time wasted on reconnection attempts. Download: 64bit: http://www.gat3way.eu/poc/hashkill-0.2.4-x86_64.tgz32-bit: http://www.gat3way.eu/poc/hashkill-0.2.4-x86.tgz |
|
|
|
|
|
kripz
|
|
July 03, 2011, 10:33:09 AM |
|
Is your hasher optimised for the 5000 series? I seem to get get less hash rate (50+) and also less shares per hour.
As compared to what? poclbm/phatk based hashers, specifically phoenix and diablo. EDIT: Actually may of been GPU speed drop issues... ill keep an eye on the new version. |
|
|
|
|
gat3way (OP)
|
|
July 03, 2011, 10:34:09 AM |
|
What's your hardware, SDK version and catalyst version?
|
|
|
|
|
|
kripz
|
|
July 03, 2011, 10:42:09 AM |
|
5770, sdk 2.4, cat 11.5. debian 32bit.
another machine same software but 5850.
See post #348, ill post back when i get an hours run out of it.
|
|
|
|
|
gat3way (OP)
|
|
July 03, 2011, 10:44:31 AM |
|
Hm interested in results with the latest version.
|
|
|
|
|
|
kripz
|
|
July 03, 2011, 11:03:39 AM |
|
Still having issues with flexible mining proxy. This is the only client that crashes. Mining statistics...
Speed: 164 MHash/sec [proc: 18] [subm: 16] [stale: 0] [eff: 88%]
Long polling: got new block!
Speed: 159 MHash/sec [proc: 54] [subm: 39] [stale: 3] [eff: 72%] [error] (ocl_bitcoin.c:141) Cannot authenticate! Speeds dropping slightly, though this was only 30 minutes testing. I get 180mh/s constant with phoenix and diablo. |
|
|
|
|
gat3way (OP)
|
|
July 03, 2011, 11:18:14 AM |
|
You don't need to use the mining proxy now. The failover functionality is built-in already.
|
|
|
|
|
|
kripz
|
|
July 03, 2011, 11:52:08 AM |
|
I'm not using the proxy for that.
|
|
|
|
|
antares
|
|
July 03, 2011, 04:28:20 PM |
|
Hi Get3way,
I downloaded your tool yesterday, it really increases my hashing rate about > 20% (from 193MH/s on an 960/1200 OC HD 6770 to 212MH/s).
However, it also increased stale share rate from 1% to about 6.5%. I'm currently mining @bitcoins.lc
Also I'd like to ask whether hashkill utilizes CUDA as available. Running an openCL kernel on an nvidia card would seem somewhat unlogical to me.
If you need more data for debugging, feel free to pm me, otherwise, great work, keep up with it, and I'm really eager to see the sources being released soon too!
|
|
|
|
|
|
|
SkipDaShu
Newbie
Offline
Activity: 27
Merit: 0
|
|
July 03, 2011, 10:09:37 PM |
|
Can't download the binaries - Ditto |
|
|
|
|
|
Keninishna
|
|
July 04, 2011, 04:27:10 AM |
|
I was able to download and update and works great! except on one of my rigs one of the 6950s overheated past 109c!! fan was at 100% too. Usually it would turn the adapter off but for some reason it didn't. I'm going to RMA the card as it wasn't even overclocked anyways.
|
|
|
|
|
|
gat3way (OP)
|
|
July 04, 2011, 06:09:36 AM |
|
Server had problems...it should be available now.
|
|
|
|
|
|
antares
|
|
July 04, 2011, 06:49:59 AM |
|
hey gat3way,
I found that your nice tool stalls when it looses connectivity.
It would be nice if it could auto-resume connection to the pool if interrupted, as at least here in germany all internet connections are interrupted at least every 24 hrs - gateway vendors have countered this disconnect to fall into the night time, so the rigs are usually offline for some time every day which is uncool. It'd also be nice to have a socket spawn from hashkill that allows reading of basic program statistics, so we can develop our tools around yours. It'd also be awesome if hashkill had a switch to show all avail plugins - eg I've been searching for some tool that can use a GPU to get around salted MD5 ($1$, ya know:-D). Still the question remains whether hashkill has native CUDA support.
|
|
|
|
|
|
