miner battle: z-enemy 1.16 (x64) vs. t-rex 0.5.7 [x16r / ravencoin]

[kerzNOberz]

Head to Head test of Z-enemy 1.16 Vs t-rex 0.5.7 (X16R Ravencoin)


I've been wanting to compare performance between z-enemy and t-rex on the X16R algorithm for some time. This will be a test done in the vein of JackIt's tests in the past, where I ask which miner puts more coins in my wallet?



Setup: For this first test, I'm using a 4 GPU rig with Zotac 1080 Ti Minis running Windows 10 x64. I started an instance of each miner at the same time (using 2 GPUs each) running on the same pool (Ravenminer) and the same machine. The miners will run for ~12 hours (started around 8AM PST 8/15), I'll stop them simultaneously, and we'll see how many coins are in the 2 wallets. I will likely run this test 2-3 times to ensure that the results are consistent.

Overclock: 100% TDP, +110 core clock, stock memory


Drivers: 398.82


Miners: Z-enemy 1.16 x64,  CUDA 9.2, intensity 22 (thread here)   vs.        T-rex 0.5.7 , CUDA 9.2 , intensity 22 (thread here) . Both miners have a 1% dev fee. Running auto (server set) difficulty on both miners, it appears to stabilize in the 60-75 range. For the first test Z-enemy will use GPU0&1 and t-rex will use GPU2&3. For the second round, I'll switch which GPUs each software uses to control for variations in hardware & PCIe slot.



Results:

ROUND #1: 650 minutes

z-enemy 1.16 : 38.63 RVN: pool link
t-rex 0.5.7 : 42.50 RVN (+10.0%) : pool link ***** WINNER  ******* (GPU2&3)

ROUND #2: 750 minutes

z-enemy 1.16 : 109.63 RVN (+7.3%): pool link ***** WINNER   ******* (GPU2&3)
t-rex 0.5.7 : 102.16RVN : pool link


Round #3: 250 minutes
z-enemy 1.16 : 39.79 RVN (+13.7%) : pool link ***** WINNER   ******* (GPU2&3)
t-rex 0.5.7 : 35.98 RVN : pool link


TEST FAILED!!!
GPU2&3 are winning every test (rig unbalanced). I'm going to redo the test on another rig in hopes of conclusive results.

new test here: https://bitcointalk.org/index.php?topic=4907176

[kerzNOberz]

GPU-Z shot of one of the 1080 Tis:



Z-enemy 1.16 starting:



T-rex 0.5.7 starting:

[Quake4]

please highlight links to pool

[kerzNOberz]

please highlight links to pool

done.

[kerzNOberz]

ROUND #1 complete. I will post results here soon. On to ROUND #2 , I switched which set of 2 GPUs is used for each miner.

[kerzNOberz]

ROUND #1: ~11 hours

z-enemy 1.16 : 38.63 RVN: pool link
t-rex 0.5.7 : 42.50 RVN (+10.0%) : pool link ***** WINNER ROUND #1  *******


t-rex takes round #1 by a solid 10% in earnings. could be due to the variability in the X16R algorithm, so we'll need a few more rounds before we declare t-rex the winner.

[Quake4]

Remove d=15. Its to slow for 2x1080Ti. And next round run without -i. On default intencity.

[kerzNOberz]

Remove d=15. Its to slow for 2x1080Ti. And next round run without -i. On default intencity.

I'm not running static difficulty (see my post). I will probably test intensity at a later time.

[sky999]

Dude, this is two different miners and they need different intensity --i params for optimal working! It looks like --i 22 is optimum for t-rex but it isn't for z-enemy. Z-enemy need -i 19/20 param it's optimum for that miner.

[kerzNOberz]

Dude, this is two different miners and they need different intensity --i params for optimal working! It looks like --i 22 is optimum for t-rex but it isn't for z-enemy. Z-enemy need -i 19/20 param it's optimum for that miner.

Nah, I’ve optimized these in the past on my system and z enemy performs better at 21.5/22 intensity. I can test them again at different intensities (or their standard intensities). This is a test of the intensities that run the best on my machine.

[kerzNOberz]

ROUND #2: COMPLETE!

z-enemy 1.16 : 109.63 RVN (+7.3%): pool link ***** WINNER   *******
t-rex 0.5.7 : 102.16RVN : pool link

Round 2 we have a different winner, z-enemy by 6%! Round 3 begins.

[dragonmike]

ROUND #2: COMPLETE!

z-enemy 1.16 : 109.63 RVN (+7.3%): pool link ***** WINNER   *******
t-rex 0.5.7 : 102.16RVN : pool link

Round 2 we have a different winner, z-enemy by 6%! Round 3 begins.

...which shows that your rounds are way too short to give any meaningful result. Especially with an algo like x16R... and even more today when the network is having a massive difficulty rape.

[ekbdanilindmitriy]

nice