Quote from: zielar on March 01, 2019, 02:18:06 PM

Quote from: racminer on February 28, 2019, 12:57:55 PM

Quote from: zielar on February 28, 2019, 05:57:51 AM

Quote from: racminer on February 27, 2019, 12:46:19 PM

Quote from: holy_ship on February 27, 2019, 02:30:23 AM

You, stubborn boyz, don't get simple thing: bounty is 100% compressed, so you need only -c switch.
For abandoned wallets you 100% need both -u and -c switches.
That's 2x drop.

bloom filter with thousands of addressed also cannot be free. Here you get another ~50% drop.

So, 1 address vs thousands is really around "3X difference".

.........................

.....................

Thanks.

One more thing, about -b -t -p (to Zielar)

Default setting:
~/BitCrack/bin$ ./clBitCrack -d 1 15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
Ellesmere 16/6471MB | 1 target 48.35 MKey/s (1,997,537,280 total) [00:00:39]

My setting:
:~/BitCrack/bin$ ./clBitCrack -d 1 -b 72 -t 256 -p 2048 15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
Ellesmere 2304/6491MB | 1 target 107.70 MKey/s (868,220,928 total) [00:00:06]

racminer - I know that multiplying the value of -b x2 does not affect the result, however I found (in my case) on other cards - a setting that is definitely better. And without hiding the fact that the -p indicator I have exactly the same as you (2560), check what result will be at the setting: -b 36 -t 512 -p 2560 ... if it does not move, reduce the -p value... and share the result... :-)

./clBitCrack -r -c -u -d 1 -b 36 -t 256 -p 2048 -o res.txt -i btc.txt
[2019-02-28.13:53:24] [Info] Compression: both
Ellesmere 1216/6512MB | 2749473 targets 35.61 MKey/s (603,979,776 total) [00:00:15]

./clBitCrack -r -c -u -d 1 -b 72 -t 256 -p 2048 -o res.txt -i btc.txt
[2019-02-27.13:58:26] [Info] Compression: both
Ellesmere 2368/6471MB | 2749473 targets 46.55 MKey/s (1,659,358,937,088 total) [10:01:53]

racminer.... try -t 512 with -b 36... no 256

Rx480 has a limit ... You can't have -t higher than 256.