miner battle: z-enemy 1.17 vs t-rex 0.6.1 vs spmodgit-9 [x16r] FINISHED

[abudfv2008]

round 3 complete, onto round 4

Thats what I was talking about. 1gpu and 10hours is not enough to exclude luck factor.
You can get 10 times black in roulette while each time chances are equal.

[kerzNOberz]

round 3 complete, onto round 4

Thats what I was talking about. 1gpu and 10hours is not enough to exclude luck factor.
You can get 10 times black in roulette while each time chances are equal.

talk about false equvalencies and hyperbole ......

are you arguing hash order only changes once per hour? it's unclear. i agree longer tests are somewhat "better", but for now this will give me a rough idea of which miner is producing more coins on average.

[kerzNOberz]

one suggestion i was given was to benchmark X16S as each block has an equivalent difficulty which should give more straightforward & less random results

i'll try that next

[kerzNOberz]

started a new experiment comparing intensity 20 (default) vs 21 vs 23 on t-rex 0.5.7

my plan is to try to find an optimal intensity for both t-rex and z-enemy separately and then to compare those head 2 head eventually

[Lukras]

started a new experiment comparing intensity 20 (default) vs 21 vs 23 on t-rex 0.5.7

my plan is to try to find an optimal intensity for both t-rex and z-enemy separately and then to compare those head 2 head eventually

   

just do not forget to lay out the number of coins mined in your trials, or else it will be a fake, z-anemy with a smaller hash percent of 2-3 gives more coins

[abudfv2008]

round 3 complete, onto round 4

Thats what I was talking about. 1gpu and 10hours is not enough to exclude luck factor.
You can get 10 times black in roulette while each time chances are equal.

talk about false equvalencies and hyperbole ......

are you arguing hash order only changes once per hour? it's unclear. i agree longer tests are somewhat "better", but for now this will give me a rough idea of which miner is producing more coins on average.

I think you dont get it. Im talking about luck to solve a share. 3 instances of the same miner would find different number of  shares, and the difference could be the same 10 20%. The only way to equalize chances is increasing the quantity of gpu or time.

[kerzNOberz]

new version of t-rex is out: 0.6.1

i'm gonna go ahead and compare the fastest t-rex intensity on my machine [24] vs the fastest z-enemy [23] vs z-enemy internal fastest [20].

i'll let this run for at least 24 hours, hopefully more like 36 for each round and we'll see if z-enemy is still the winner.

[kerzNOberz]

restarting the round, power outage last night and one of my miners failed to start up automatically after the reboot

[areyouathief]

restarting the round, power outage last night and one of my miners failed to start up automatically after the reboot

z-enemy 1.17 available:
-  Major performance improvements: 5-10% for X16R & X16S, XDNA (hex), x17, Bitcore(BTX), c11, Sonoa, Renesis, Aergo

[kerzNOberz]

comparing z-enemy 1.17 now

[areyouathief]

comparing z-enemy 1.17 now

me too,
1.17 vs 0.6.1
both at 24 intensity

[GeePeeU]

Get SPmodgit-9 and compare.

All of these miners are pushing updates faster than a concrete test can be done.

[kerzNOberz]

z-enemy 1.17 appears significantly faster than 1.16

doing one final round to compare the latest versions of all 3 miners (including spmodgit9)

[Johnjay06]

Update on this?

[bubbAJoe]

spmodgit-10 vs t-rex 0.6.3 vs enemy 1.18?

[dragonmike]

Acenun vs Avermore vs Kl0nLutiy vs MadKernel vs GatelessGate Sharp?

[ender2002]

I'm testing t-rex and z-enemy on x16r with 4 rigs (31 various GPUs : GTX 1060,1070 and 1070ti) and I've  got strange result.

t-rex 0.6.10  hash rate from 320 Mhs to 540 Mhs
z-enemy 1.20  hash rate  almost constant between 418 Mhs to 433 Mhs

Curious the average of t-rex  (320+540)/2 = 430 Mhs is almost the same as the hash rate of z-enemy 418 to 433.

I prefer for now z-enemy being more constant over t-rex

[mercoinz]

update?

I think we got z-enemy 1.22 and t-rex .7 now iirc?

[Multipulty2018]

z-enemy:

[NOTICE ] 18/10/24 09:55:26 Block 417717, difficulty 79272.444
[X16    ] 18/10/24 09:55:26 Seq: CubShaCubShbHamShaCubLufLufWrlLufCubHamKckHamFug
[X16    ] 18/10/24 09:55:26 Raw: 7F7DBF766E67B4BC
[NOTICE ] 18/10/24 09:55:27 Shares: 67 (A:100.00%, R:0.00%), Diff:0.898, 42.80MH/s, 90ms - OK
[INFO   ] 18/10/24 09:55:32 GPU#1: GeForce GTX 1080, 19.08MH/s
[NOTICE ] 18/10/24 09:55:32 Shares: 68 (A:100.00%, R:0.00%), Diff:0.117, 42.87MH/s, 113ms - OK
[NOTICE ] 18/10/24 09:55:51 Shares: 69 (A:100.00%, R:0.00%), Diff:0.156, 42.92MH/s, 97ms - OK
[NOTICE ] 18/10/24 09:55:52 Shares: 70 (A:100.00%, R:0.00%), Diff:0.063, 42.98MH/s, 105ms - OK
[NOTICE ] 18/10/24 09:55:53 Shares: 71 (A:100.00%, R:0.00%), Diff:0.554, 43.03MH/s, 105ms - OK
[NOTICE ] 18/10/24 09:56:03 Shares: 72 (A:100.00%, R:0.00%), Diff:0.216, 43.08MH/s, 83ms - OK
[NOTICE ] 18/10/24 09:56:05 Shares: 73 (A:100.00%, R:0.00%), Diff:0.222, 43.12MH/s, 82ms - OK
[INFO   ] 18/10/24 09:56:06 GPU#0: GeForce GTX 1080, 18.57MH/s
[INFO   ] 18/10/24 09:56:06 Uptime: 0 days, 0 hours, 4 minutes, 53 seconds.
[NOTICE ] 18/10/24 09:56:07 Shares: 74 (A:100.00%, R:0.00%), Diff:0.068, 43.16MH/s, 97ms - OK
[INFO   ] 18/10/24 09:56:08 GPU#2: GeForce GTX 1060 3GB, 8905.62kH/s
[NOTICE ] 18/10/24 09:56:08 Shares: 75 (A:100.00%, R:0.00%), Diff:0.146, 43.21MH/s, 83ms - OK
[NOTICE ] 18/10/24 09:56:24 Shares: 76 (A:100.00%, R:0.00%), Diff:0.118, 43.25MH/s, 96ms - OK
[NOTICE ] 18/10/24 09:56:35 Shares: 77 (A:100.00%, R:0.00%), Diff:0.198, 43.29MH/s, 6172ms - OK

t-rex:

20181024 09:58:35 WARN: GPU #0: GeForce GTX 1080, intensity set to 20, 1048576 cuda threads
20181024 09:58:35 WARN: GPU #1: GeForce GTX 1080, intensity set to 20, 1048576 cuda threads
20181024 09:58:36 WARN: GPU #2: GeForce GTX 1060 3GB, intensity set to 20, 1048576 cuda threads
20181024 09:58:36 ApiServer: HTTP server started on 0.0.0.0:4067
20181024 09:58:36 ApiServer: Telnet server started on 0.0.0.0:4068
20181024 09:58:36 WARN: New difficulty: 8 (0.03125)
20181024 09:58:36 x16r block 417718, diff 78860.522
20181024 09:58:38 Hash order CEC13D87C50CC990
20181024 09:58:38 FugWrlFugBmwJh5ShbShvCubFugSkeBlkFugFugSmdSmdBlk
20181024 09:58:39 [ OK ] 1/1 - 55.25 MH/s, 109ms
20181024 09:58:39 [ OK ] 2/2 - 56.13 MH/s, 93ms
20181024 09:58:43 [ OK ] 3/3 - 56.72 MH/s, 109ms
20181024 09:58:45 [ OK ] 4/4 - 56.83 MH/s, 124ms
20181024 09:58:48 [ OK ] 5/5 - 56.82 MH/s, 109ms
20181024 09:58:48 GPU #0: GeForce GTX 1080 - 22.90 MH/s, [T:68C, P:199W, F:100%, E:173kH/W]
20181024 09:58:48 GPU #1: GeForce GTX 1080 - 23.18 MH/s, [T:62C, P:209W, F:100%, E:168kH/W]
20181024 09:58:48 GPU #2: GeForce GTX 1060 3GB - 10.74 MH/s, [T:60C, P:114W, F:70%, E:138kH/W]
20181024 09:58:48 Uptime: 12 secs
20181024 09:58:50 [ OK ] 6/6 - 56.80 MH/s, 93ms

[impynick]

as you can see the miners started on different sequences. So as you might know x16r algo fluctuates based on the algo its on. Try to have it both be the same algo then come back and update.