However since 0.8.2 my 1070 greatly outperforms my 1070ti's on Lyra2z.
1070 avg hash 3954 KH/s
1070ti avg hash 3220 KH/s
any ideas how? I've got 4 different 1070ti's and none come close to my normal 1070....
Topic: CryptoDredge 0.27.0 — CUDA Miner - page 45. (Read 85990 times)
love the improvements.
However since 0.8.2 my 1070 greatly outperforms my 1070ti's on Lyra2z.
1070 avg hash 3954 KH/s
1070ti avg hash 3220 KH/s
any ideas how? I've got 4 different 1070ti's and none come close to my normal 1070....
However since 0.8.2 my 1070 greatly outperforms my 1070ti's on Lyra2z.
1070 avg hash 3954 KH/s
1070ti avg hash 3220 KH/s
any ideas how? I've got 4 different 1070ti's and none come close to my normal 1070....
using windows version here mixed with some autoswitch software that fail to read api response since 8.2, had no problem with version 8.0 or 7
same here. Windows + Awesome Miner.
What a Windows version do you use? Thanks for your help! ...
question. you can make under the algoritm HEX, it's possible, you would be the first))))
question. you can make under the algoritm HEX, it's possible, you would be the first))))
CD .6 and up are no longer working on PHI2 after fork...please advise
Cryptodredge has problems with Lux's smart contracts.We'll try to fix it as soon as possible. Sorry for the inconvenience!
question. you can make under the algoritm HEX, it's possible, you would be the first))))
Some users reported hashrate drops for upper end cards like 1080 TI on 0.8.2, should we wait for future releases for improvements on 1080 TI ?..
Also what Overclock settings would you recommend for 1080 TI when mining Lyra2Rev2 ?..
All the Best
Also what Overclock settings would you recommend for 1080 TI when mining Lyra2Rev2 ?..
All the Best
using windows version here mixed with some autoswitch software that fail to read api response since 8.2, had no problem with version 8.0 or 7
same here. Windows + Awesome Miner.
using windows version here mixed with some autoswitch software that fail to read api response since 8.2, had no problem with version 8.0 or 7
the api support w/ awesome miner seems a little wonky..i'm only getting readouts from 1/4 of my miners using 0.8.2. Anyone else getting the same?
Does CryptoDredge close the sockets properly before exiting?
I see a lot of TIME_WAITs when CryptoDredge is running, and they slowly disappear when CryptoDredge is stopped.
If CryptoDredge is started after 3-4 minutes, the api seems to start ok.
I see a lot of TIME_WAITs when CryptoDredge is running, and they slowly disappear when CryptoDredge is stopped.
If CryptoDredge is started after 3-4 minutes, the api seems to start ok.
yup, often the miner tries to use the default API bind address and port (127.0.0.1:4068) instead of using the address from its command line arguments.
With 0.8.2 the API server is not always started as set by the command line.
Please help to fix API issue ASAP. without it , could not use the miner on awesome miner.
thanks
thanks
+1 on API fix, good miner but unusable by most of us in actual state!
It still mines correctly but you cannot see what you are making and awesome miner will restart the miner because the accepted share does not increase.. need a fix quickly
This bug has already been fixed, update will be delivered soon. What OS do you use?
+1 on API fix, good miner but unusable by most of us in actual state!
the api support w/ awesome miner seems a little wonky..i'm only getting readouts from 1/4 of my miners using 0.8.2. Anyone else getting the same?
Yep, that is a known issue. The API often does not start since version 0.8.0. You might try to use 0.7.0 (Windows version is CUDA 9.2 only) Apologize!Please help to fix API issue ASAP. without it , could not use the miner on awesome miner.
thanks
It still mines correctly but you cannot see what you are making and awesome miner will restart the miner because the accepted share does not increase.. need a fix quickly
the api support w/ awesome miner seems a little wonky..i'm only getting readouts from 1/4 of my miners using 0.8.2. Anyone else getting the same?
Yep, that is a known issue. The API often does not start since version 0.8.0. You might try to use 0.7.0 (Windows version is CUDA 9.2 only) Apologize!Please help to fix API issue ASAP. without it , could not use the miner on awesome miner.
thanks
With 0.8.2 the API server is not always started as set by the command line.
How to set the intensity of the first graphics card 3 and the second 6?
No way. As a workaround for this issue, you might use a few CryptoDredge instances with -d option.e.g.:
Code: (first.bat)
CryptoDredge -a -o stratum+tcp:// -u -p -d 0 -i 3
Code: (second.bat)
CryptoDredge -a -o stratum+tcp:// -u -p -d 1
Can we expect this option? this is very important
yup, often the miner tries to use the default API bind address and port (127.0.0.1:4068) instead of using the address from its command line arguments.
thanks to the development team. this is the best miner for the whole time, this is the best team.
Well done.
Well done.
the api support w/ awesome miner seems a little wonky..i'm only getting readouts from 1/4 of my miners using 0.8.2. Anyone else getting the same?
Yep, that is a known issue. The API often does not start since version 0.8.0. You might try to use 0.7.0 (Windows version is CUDA 9.2 only) Apologize!Does CryptoDredge close the sockets properly before exiting?
I see a lot of TIME_WAITs when CryptoDredge is running, and they slowly disappear when CryptoDredge is stopped.
If CryptoDredge is started after 3-4 minutes, the api seems to start ok.
the api support w/ awesome miner seems a little wonky..i'm only getting readouts from 1/4 of my miners using 0.8.2. Anyone else getting the same?
Yep, that is a known issue. The API often does not start since version 0.8.0. You might try to use 0.7.0 (Windows version is CUDA 9.2 only) Apologize! 
0.8 to 0.8.2 was a big boost on lyra2z for the gtx1070 (2500 kh/s to 3200 kh/s)
However, 0.8 to 0.8.2 the hashrate regressed on lyra2z for the gtx1070ti (3300 kh/s to 2700 kh/s)
However, 0.8 to 0.8.2 the hashrate regressed on lyra2z for the gtx1070ti (3300 kh/s to 2700 kh/s)
the api support w/ awesome miner seems a little wonky..i'm only getting readouts from 1/4 of my miners using 0.8.2. Anyone else getting the same?
Thank you!
Jump to: