Topic: EWBF's CUDA Zcash miner - page 223. (Read 2164327 times)

Thanks for the help
I kept finding time based which wasn't what I wanted.

what are you talking about ? what solvers ? i dont understand without readme file ((

Tested 6*1070 Palit SJS rig , ver. 010 giving me more hash than 020.
I've tried all the solvers , only 1 is working to my cards...

I am glad that we can confirm the same results. Solver 0 forced is giving the best results and also two instances do not bring more sols

Final result

6x1070 rig, 2650sols/s 145/590 @60% tdp, had to reduce OC a bit to be stable. solver 0 forced, the best so far. Multiple instance of the miner seems to make it unstable now, with 3 it's totally unstable, with 2, it's pretty stable, but don't get more sols than with 1 instance. so about 2/2.5% gain from 0.0.1b

Yes, but each time i restart the miner it chooses different solver for the same card even , also i seem to be getting always better results on solver 0.

With what solver u get those numbers? can u post an example of ur bat file

0.1.0b dont have this behaviour. it just happens with the new.

Like this

each time miner exit, it will restart itself.

Cheers 

Does anyone know  how to  use -eexit so it will restart my batch file?

good job
http://i90.fastpic.ru/big/2017/0117/4a/510ea0570298562db0d9cbc90f692f4a.jpg

This actually not a problem. It happened by many reasons: first low precise of timers, load of pool, and this is not a ping it a time in milliseconds from finding a solution to receive a pool answer.

i have the strange issue that the yubmit time sometimes multiply by 10*

NFO 21:33:10: GPU1 Accepted share 36ms [A:257, R:1]
INFO 21:33:15: GPU1 Accepted share 58ms [A:258, R:1]
GPU0: 260 Sol/s GPU1: 271 Sol/s
Total speed: 531 Sol/s
INFO 21:33:19: GPU0 Accepted share 43ms [A:247, R:0]
INFO 21:33:20: GPU0 Accepted share 480ms [A:248, R:0]
INFO 21:33:21: GPU1 Accepted share 36ms [A:259, R:1]
INFO 21:33:27: GPU0 Accepted share 1639ms [A:249, R:0]
INFO 21:33:27: GPU0 Accepted share 644ms [A:250, R:0]
INFO 21:33:31: GPU0 Accepted share 38ms [A:251, R:0]
INFO 21:33:35: GPU0 Accepted share 43ms [A:252, R:0]
INFO 21:33:35: GPU1 Accepted share 39ms [A:260, R:1]
INFO 21:33:37: GPU0 Accepted share 40ms [A:253, R:0]
INFO 21:33:42: GPU0 Accepted share 46ms [A:254, R:0]
INFO: Detected new work: c6b888b78228421bcb4d
INFO 21:33:43: GPU1 Accepted share 33ms [A:261, R:1]
INFO 21:33:45: GPU0 Accepted share 40ms [A:255, R:0]
INFO 21:33:46: GPU0 Accepted share 40ms [A:256, R:0]
GPU0: 266 Sol/s GPU1: 268 Sol/s
Total speed: 534 Sol/s
INFO 21:33:51: GPU0 Accepted share 38ms [A:257, R:0]
INFO 21:34:01: GPU0 Accepted share 106ms [A:258, R:0]
INFO 21:34:01: GPU1 Accepted share 88ms [A:262, R:1]
INFO 21:34:03: GPU0 Accepted share 40ms [A:259, R:0]
INFO 21:34:06: GPU0 Accepted share 700ms [A:260, R:0]
INFO 21:34:09: GPU1 Accepted share 3309ms [A:263, R:1]
INFO 21:34:09: GPU0 Accepted share 723ms [A:261, R:0]
INFO 21:34:11: GPU0 Accepted share 40ms [A:262, R:0]

Seems the optimization bring for me the same symptoms i got on nicehash 0.5c, unstability at higher overclock, i'm playing with settings right now.

Thanks for the infos about solvers. Trying to find again the sweet spot.

EDIT : got the same speed 2590s/sols (6x1070 rig) i was getting before with 0.0.1b, but with lower overclock (120/500 down from 150/600) and one instance, room to improve this result for sure

Try another solvers. Because on my rig i get 450 per one 1070 with new version and 440 with 0.1.0b

the release not good.
whit 0.1.0b 5x1070=2150
whit 0.2.0b 5x1070=2120 ??!?

All solvers is a variations of my old solver for example solver 3 is solver from version 0.6.0b for old cards. 0 is solver from version 0.1.0b but with optimizations in code. Solver 2 is most stable and 1 is a hybrid between 0 and 2.

Nice thanks

This version still struggle with threads, have to start 3 instances of the miner to maximize output as before. Performance of solver 0 and 1 are really close, but i see more stability, and a bit more sol on solver 1, also seems to get a bit of rejected shares on solver 0 when i don't have any in solver 1

Ok i will add custom file name

Solver 0 seems to be very unstable for nvidia 1070 on my test rig, solver 1 work stable. Also yeah need logfile name pretty please can you tell us what solver is which, and also what was the solver used in previous EWBF ?

Well seems a reboot helped, solver 0 now work. weird...