More stable and higher hashrates. Enjoy.
Happy mining!
Lyra2REv2 on SM52 is 5% lower - but pool side is GOOD! On SM50 2-3% higher. |
|
|
|
 So stable... Thank YOU!
|
|
|
|
|
Commit 1004 - quark is broken... Lyra2v2 on pool side is stable! But hashrate is 2 times slower...
|
|
|
|
|
Lyra2REv2:
[2015-09-03 00:11:31] accepted: 65/66 (98.48%), 27603 kH/s (nooooo)
[2015-09-03 00:11:31] reject reason: Duplicate share.
[2015-09-03 00:11:31] enabling duplicates check feature
[2015-09-03 00:11:37] GPU #2: GeForce GTX 960, 5242
[2015-09-03 00:11:39] GPU #1: GeForce GTX 980, 11282
[2015-09-03 00:11:40] GPU #0: GeForce GTX 980, 10614
[2015-09-03 00:11:40] accepted: 66/67 (98.51%), 27332 kH/s (yes!!!)
[2015-09-03 00:11:41] accepted: 67/68 (98.53%), 27119 kH/s (yes!!!)
[2015-09-03 00:11:42] GPU #1: GeForce GTX 980, 11351
[2015-09-03 00:11:42] GPU #2: GeForce GTX 960, 6039
[2015-09-03 00:11:43] GPU #0: GeForce GTX 980, 10679
[2015-09-03 00:11:43] accepted: 68/69 (98.55%), 27335 kH/s (yes!!!)
[2015-09-03 00:11:44] accepted: 69/70 (98.57%), 27150 kH/s (yes!!!)
.......
[2015-09-03 00:13:45] GPU #1: GeForce GTX 980, 11442
[2015-09-03 00:13:46] accepted: 81/82 (98.78%), 27177 kH/s (yes!!!)
[2015-09-03 00:13:46] GPU #2: GeForce GTX 960, 6014
[2015-09-03 00:13:47] GPU #0: GeForce GTX 980, 10714
[2015-09-03 00:13:47] GPU #1: GeForce GTX 980, 11406
[2015-09-03 00:13:49] GPU #2: GeForce GTX 960, 6042
[2015-09-03 00:13:50] GPU #0: GeForce GTX 980, 10293
[2015-09-03 00:13:50] GPU #1: GeForce GTX 980, 11207
[2015-09-03 00:13:59] GPU #2: GeForce GTX 960, 6005
[2015-09-03 00:14:00] GPU #1: GeForce GTX 980, 11433
[2015-09-03 00:14:00] GPU #0: GeForce GTX 980, 10748
[2015-09-03 00:14:02] GPU #1: GeForce GTX 980, 11166
[2015-09-03 00:14:02] GPU #2: GeForce GTX 960, 5847
[2015-09-03 00:14:02] GPU #0: GeForce GTX 980, 10599
[2015-09-03 00:14:04] nonce 95ad2703 was already sent 44 seconds ago
[2015-09-03 00:14:05] GPU #1: GeForce GTX 980, 11408
[2015-09-03 00:14:05] GPU #0: GeForce GTX 980, 10748
[2015-09-03 00:14:05] GPU #2: GeForce GTX 960, 6025
[2015-09-03 00:14:08] GPU #0: GeForce GTX 980, 10376
[2015-09-03 00:14:08] GPU #1: GeForce GTX 980, 11395
[2015-09-03 00:14:08] GPU #2: GeForce GTX 960, 5952
[2015-09-03 00:14:10] GPU #0: GeForce GTX 980, 9597
[2015-09-03 00:14:10] GPU #1: GeForce GTX 980, 11207
[2015-09-03 00:14:12] GPU #2: GeForce GTX 960, 3660
[2015-09-03 00:14:13] GPU #0: GeForce GTX 980, 10680
[2015-09-03 00:14:13] GPU #1: GeForce GTX 980, 8560
[2015-09-03 00:14:15] GPU #2: GeForce GTX 960, 4690
[2015-09-03 00:14:16] GPU #1: GeForce GTX 980, 11357
[2015-09-03 00:14:16] GPU #0: GeForce GTX 980, 10782
[2015-09-03 00:14:17] nonce 88b38eb0 was already sent 45 seconds ago
[2015-09-03 00:14:18] GPU #2: GeForce GTX 960, 6019
[2015-09-03 00:14:18] GPU #1: GeForce GTX 980, 11363
[2015-09-03 00:14:18] GPU #0: GeForce GTX 980, 10519
[2015-09-03 00:14:21] GPU #2: GeForce GTX 960, 6006
[2015-09-03 00:14:21] GPU #1: GeForce GTX 980, 11376
[2015-09-03 00:14:21] GPU #0: GeForce GTX 980, 6173
[2015-09-03 00:14:23] GPU #1: GeForce GTX 980, 11357
[2015-09-03 00:14:23] GPU #2: GeForce GTX 960, 5990
[2015-09-03 00:14:24] GPU #0: GeForce GTX 980, 10731
[2015-09-03 00:14:26] GPU #1: GeForce GTX 980, 10816
[2015-09-03 00:14:26] GPU #2: GeForce GTX 960, 6019
[2015-09-03 00:14:27] GPU #0: GeForce GTX 980, 10667
[2015-09-03 00:14:28] GPU #1: GeForce GTX 980, 11357
[2015-09-03 00:14:29] GPU #2: GeForce GTX 960, 5574
[2015-09-03 00:14:29] GPU #0: GeForce GTX 980, 10581
[2015-09-03 00:14:30] GPU #1: GeForce GTX 980, 11403
[2015-09-03 00:14:31] nonce a60a4f13 was already sent 45 seconds ago
[2015-09-03 00:14:32] GPU #2: GeForce GTX 960, 6007
[2015-09-03 00:14:32] GPU #0: GeForce GTX 980, 10748
[2015-09-03 00:14:33] GPU #1: GeForce GTX 980, 11357
[2015-09-03 00:14:38] GPU #0: GeForce GTX 980, 10714
[2015-09-03 00:14:39] GPU #2: GeForce GTX 960, 6025
[2015-09-03 00:14:43] GPU #1: GeForce GTX 980, 11433
[2015-09-03 00:14:51] GPU #0: GeForce GTX 980, 10782
[2015-09-03 00:14:51] GPU #2: GeForce GTX 960, 5242
[2015-09-03 00:14:56] GPU #1: GeForce GTX 980, 11433
[2015-09-03 00:14:58] accepted: 82/83 (98.80%), 27761 kH/s (yes!!!)
[2015-09-03 00:14:58] stratum connection reset
[2015-09-03 00:14:59] Stratum difficulty set to 4
|
|
|
|
|
Now testing lira2v2 on sm50 (750Ti).
Miner show good hashrate. On pool side (nicehash) every 2.5 minutes connection reseted (when diff go from 2 up to 4 and 40 seconds miner dont take any yay!!). Problem same.
Pool shows speed 3-6 Mh - my 2x750Ti make 8.4 Mh...
|
|
|
|
|
Commit 997 lyra2v2 is slower on sm52 (from 27.9 Mh to 26.7-27.6 Mh) and not stable in miner. sm 50 not tested.
Nicehash pool side show - not more 20Mh. when pool set diff to 8 - miner dont found any hashes. Then diff resetting to 4 and again hashes founded.GPU usage is jumping up and down.
After resetting diff on pool accepted speed is starting from zero. Stratum connection reseted.
PS. 2x980GTX and 960GTX in one rig.
|
|
|
|
Application dont exit after pool disconnect (-r 3 -R 10). Terminating thread and wait for somthing. -q dont work. I am using win10.
Mind pasting(or screenshot) the exact output at exit? How long are you waiting? I've seen the GPU threads take 10-15s to exit without an additional ctrl+c to abort them (Linux). More then 30 minutes. Last string is "terminating workio threads". Ctrl+C works good. Thats all... I'm sorry, I don't seem to be comprehending the issue. It sounds like it is working as intended. Maybe you could post the entire output from the first "CTRL_C_EVENT received, ..." line to the end? The design behavior is on first ctrl+c, we signal all threads to exit and wait for them to do so on their own. Since it may take quite some time for the current hash job to finish, a second ctrl+c will signal to abort GPU work. The application should exit very quickly after the second ctrl+c. Though I see now that we're killing the threads in the wrong order. The work from allowing the GPU threads to finish is just thrown away... Something more for the TODO list.  [2015-09-01 23:36:03]←[31m Stratum connection failed: Failed to connect to cnote.mine-pool.net port 3800: Timed out←[0m [2015-09-01 23:36:03]←[31m ...terminating workio thread←[0m [2015-09-01 23:41:09] CTRL_C_EVENT received, exiting once miner jobs complete. Ctrl+C again to abort miner jobs←[0m [2015-09-01 23:41:10] workio thread dead, exiting.←[0m |
|
|
|
Application dont exit after pool disconnect (-r 3 -R 10). Terminating thread and wait for somthing. -q dont work. I am using win10.
Mind pasting(or screenshot) the exact output at exit? How long are you waiting? I've seen the GPU threads take 10-15s to exit without an additional ctrl+c to abort them (Linux). More then 30 minutes. Last string is "terminating workio threads". Ctrl+C works good. Thats all... |
|
|
|
|
Application dont exit after pool disconnect (-r 3 -R 10). Terminating thread and wait for somthing. -q dont work. I am using win10.
|
|
|
|
Work fixed . Night to test in real world...  |
|
|
|
|
In commit 980 i have a problem whith text visualisation in Miner Control (last correct is tid xxxxxxxx, thats all...). No hash. No gpu №. but miner is working. Cant test hashrates...
On nicehash miner is faster. I go to close credit for my 980gtx and do payment for grate gob!
|
|
|
|
Edit: x11 r61 better than r57 Seeing mixed results depending on algo mined.  Can you please test r62? Is it bether than r57 on quark? x11 on 750Ti -200kh. On quark whithout changes.. |
|
|
|
|
JSON-RPS CALL FaILED... and debug... dont work. recompile and test. Download and test. QUARK.
|
|
|
|
|
Solomine is broken. PLZ look on this...
|
|
|
|
Could you test x11. I got bether results with 965 on x11.
(Reducing the instruction count but adding const memory access)
Actually, I should split all the x11 kernals from the quark kernals and tune them seperatly, because the performance is not always bether for both of them.
966 show +250kh on x11 for me. now testing 965 PS. Now on 966 quark +100 kh (49500). It`s very strange... |
|
|
|
Commit 966 is slower on home rig by 300kh (960&2x980)
Can you test commit 965 is the performance lost here or in the 966? Perfomance lost in 955 100kh (compared with commit 933), but pool side is not bad. 966 300kh lost, pool side go down 20% stable. PS. 40 minutes on nicehash speed stable 40-50MH (my 49200 now in miner), 200 kh lower then 955. Are you mixing 955 with 965? I think I will revert the 966 commit. Sorry, yes - my mistake. 965! |
|
|
|
Commit 966 is slower on home rig by 300kh (960&2x980)
Can you test commit 965 is the performance lost here or in the 966? Perfomance lost in 955 100kh (compared with commit 933), but pool side is not bad. 966 300kh lost, pool side go down 20% stable. PS. 40 minutes on nicehash speed stable 40-50MH (my 49200 now in miner), 200 kh lower then 955. |
|
|
|
|
Commit 966 is slower on home rig by 300kh (960&2x980)
Pool side is slower 10-20% (spikes to 54MH, middle speed 30-35 MH)
|
|
|
|
On nicehash i see strange things - my home rig (49400 kh) rise in 7 minutes to 65 mh, 25 minutes work on that speed, then go down to 40-44 mh an work on this speed.
P.S. Algo quark.
Check the temperature of the cards with gpu-z. If they start to trottle (reach 70 degrees +) the cards will downclock and you loose performance. This happens to one of my gtx 970 cards. Starts at 15.5MHASH and then drops to 13.8 MHASH after some minutes of mining because of trottling (quark) The gigabyte windforce oc has bether cooling and keeps a steady 16,5 MHASH You could try to overclock and overvolt the card then the trottleing will start on a higher temperature. Cards temp is 72-76 degrees, but miner show proper hasrate and freq is stable from 1340 to1400 MHz. All cards is Asus Strix. Could bee a pool problem. (difficulty) Any rejects? Rejects is very rarely, one time in a day or 2 days... |
|
|
|
On nicehash i see strange things - my home rig (49400 kh) rise in 7 minutes to 65 mh, 25 minutes work on that speed, then go down to 40-44 mh an work on this speed.
P.S. Algo quark.
Check the temperature of the cards with gpu-z. If they start to trottle (reach 70 degrees +) the cards will downclock and you loose performance. This happens to one of my gtx 970 cards. Starts at 15.5MHASH and then drops to 13.8 MHASH after some minutes of mining because of trottling (quark) The gigabyte windforce oc has bether cooling and keeps a steady 16,5 MHASH You could try to overclock and overvolt the card then the trottleing will start on a higher temperature. Cards temp is 72-76 degrees, but miner show proper hasrate and freq is stable from 1340 to1400 MHz. All cards is Asus Strix. |
|
|
|
|
Show Posts
