Pages:
Author

Topic: 3% faster mining with phoenix+phatk for everyone - page 5. (Read 36831 times)

hero member
Activity: 551
Merit: 500

FYI, You can make the identical change to phoenix+poclbm with the same 2% increase in speed.

Do tell, If theres a simple file to replace that you can upload i'll definitly Tip you
Winx86 GUIminer-poclbm

http://www.mediafire.com/?jth8eicn9iifnlf

Extract contents to the location of your guiminer folder and allow them to replace the existing files.
newbie
Activity: 4
Merit: 0
Thank you Smiley

5830 - 314 -> 324 (1025/300)
5830 - 308 -> 316 (1000/300)
5850 - 370 -> 379 (930/300)

I've 57MHps more - almost 3% Cheesy

I sent small donations.
member
Activity: 90
Merit: 10
5850 890/300: 345 -» 355
5850 825/300: 318 -» 325
5850 900/300: 344 -» 355

donation on its way thx.
member
Activity: 99
Merit: 10
I'm still looking at the same rejection statistics after 1100 shares.  Thanks!
full member
Activity: 126
Merit: 100
Sapphire 5870 @ 1000/347 before 442.7 Mhash/sec after 452.1 Mhash/sec overall an increase of 2.1%
newbie
Activity: 41
Merit: 0
from 402 -> 415 thanks
mrb
legendary
Activity: 1512
Merit: 1027
I was wondering when the community would discover this optimization... nice one bitless :-)

For the record, hdminer has implemented this maj() optimization since day 1:
Code:
       # ibit_extract patched to BFI_INT at runtime
        $code .=
        "    ixor $tmp0, $a, $b\n".
        "    ibit_extract $tmp0, $a, $c, $tmp0\n";

Phoenix is probably very close to hdminer's performance now, on HD 69xx.
hero member
Activity: 504
Merit: 502
Nice, avg about 2% mhash boost at same clocks. I notice no additional stales, still hovering at 1%
newbie
Activity: 28
Merit: 0
Seriously, the Ma() function is soo deeply burried, so that if it was wrong, by the principle of good hashing function like SHA256 is, all the hashes would fail.

So, if it can find some good results, all are, with 99.999999999999% probability correct, too.

More like 2^-128 if not less Smiley
hero member
Activity: 531
Merit: 505
Seriously, the Ma() function is soo deeply burried, so that if it was wrong, by the principle of good hashing function like SHA256 is, all the hashes would fail.

So, if it can find some good results, all are, with 99.999999999999% probability correct, too.
newbie
Activity: 13
Merit: 0
I want to minimize the expression applying Karnaugh. So I need the main expression that is used on the kernel. But i can't figure out with it.
full member
Activity: 216
Merit: 100
Just tossing my confirmations out there:
...
So, the increase appears to also cause additional rejects that should be discounted from total increase gain, cutting it down a full 1% in my case.

This is really not good. I honestly do not know why this would happen; are you sure it is related to the patch and isn't a result in the general randomness when searching for solutions? Perhaps someone else, more familiar with bitcoin mining than me, can chime in?


I'm not seeing this issue with my miners. They range from 0.12% to 2.07% stale. A variance that I'd say rules out your patch being the cause of any supposed increased stales.
full member
Activity: 213
Merit: 100
Neat-o-rama! Somehow I still don't believe you (and my eyes) Smiley

I do 370 Mhashes with poclbm and the new formula (365 without).
I do 380 Mhashes with phatk and the new formula (310 without).

So, really, +2.63% between poclbm and phatk with the new formula.
sr. member
Activity: 418
Merit: 250
WoW Shocked
310 to 380 Mhash (+18.42%) ! AWESOME! Thank you!

Neat-o-rama! Somehow I still don't believe you (and my eyes) Smiley


I noticed he's using Crossfire on those cards, perhaps the kernel patch somehow makes up for % loss due to using crossfire?
newbie
Activity: 28
Merit: 0
WoW Shocked
310 to 380 Mhash (+18.42%) ! AWESOME! Thank you!

Neat-o-rama! Somehow I still don't believe you (and my eyes) Smiley
newbie
Activity: 28
Merit: 0
can't do it Sad

Yes, you can Smiley what you've done is the CH function, not MA. Now you can build MA on top of it. I don't think this belongs to this thread though, so you can pm me and we'll figure it out. Alternatively, you can ask someone around you for help - two heads are better than one.
newbie
Activity: 28
Merit: 0
Just tossing my confirmations out there:
...
So, the increase appears to also cause additional rejects that should be discounted from total increase gain, cutting it down a full 1% in my case.

This is really not good. I honestly do not know why this would happen; are you sure it is related to the patch and isn't a result in the general randomness when searching for solutions? Perhaps someone else, more familiar with bitcoin mining than me, can chime in?

newbie
Activity: 28
Merit: 0

FYI, You can make the identical change to phoenix+poclbm with the same 2% increase in speed.

Do tell, If theres a simple file to replace that you can upload i'll definitly Tip you
Winx86 GUIminer-poclbm

at the office now, no access to the miners, I'll take a look once I get home. In the meantime, search for .cl files and see if you have any Ma (or, even better, amd_bytealign) strings in them and take it from there.
member
Activity: 84
Merit: 10
Just tossing my confirmations out there:

Sapphire 5830s:

Pair 1:  264 Mhash/sec -> 271 Mhash/sec (each) at 875 MHz GPU, 900 MHz RAM (2.58% increase)
Pair 2:  273 Mhash/sec -> 281 Mhash/sec (each) at 900 MHz GPU, 600 MHz RAM (2.84% increase)

I'm also tracking Rejected shares.

Before Patch:
Pair 1:  ~2.6% rejects (after 800+ shares)
Pair 2:  ~3.2% rejects (after 800+ shares)

After Patch:
Pair 1:  ~3.0% rejects (after 650+ shares)
Pair 2:  ~4.0% (after 750+ shares)

So, the increase appears to also cause additional rejects that should be discounted from total increase gain, cutting it down a full 1% in my case.
legendary
Activity: 1428
Merit: 1001
Okey Dokey Lokey

FYI, You can make the identical change to phoenix+poclbm with the same 2% increase in speed.

Do tell, If theres a simple file to replace that you can upload i'll definitly Tip you
Winx86 GUIminer-poclbm
Pages:
Jump to: