-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 1.4.4 - wonderful results on GTX 1070 neoscrypt! #182
Comments
We are waiting for the description of the parameter M in https://github.com/nicehash/excavator/tree/master/nvidia#neoscrypt |
We didn't do any speed improvements for 1080 (Ti) cards so your results are as expected :) Regarding the M parameter, the current version of excavator includes different implementations of neoscrypt - kernels might vary a bit from one mode to another and some modes work better on the specific card than others. For example, you'll notice that 1070 card uses mode 2 while 1080 uses mode 3. We opened the M parameter to the API because on cards that are not optimized (all Maxwell cards for example) different mode could perform better than the default one. |
Btw, as always.. Thanks for the feedback! :) |
@dropky Thanks for the info!
|
I'm not sure but for my set up, the benchmark result for my 2 1080tis increased from 4.01(1.4.3) to 4.11(1.4.4) MH/s for both, |
@kingyem Does memory overclocking affect neoscrypt?
|
@EvgeniyKorepov I did the overclock for core and memory for gaming actually, and was lazy to setup profiles for different usages, so i stuck with the same settings for all application, not efficient i know. tried playing around with the values for M with values 4 and 5, it resulted in a significant reduction from 4.11 to 3.13 or so MH/s for both cases, so i just left it as the default setting great work by the team,kudos |
Sorry guys, I have to ruin the party: #184 |
Algorithm neoscrypt.
GTX 1070 x 5 (TDP/Core/Memory=95/90/0) 🥇 👍
GTX 1080 (TDP/Core/Memory=100/100/0)
GTX 1080 Ti (TDP/Core/Memory=100/130/200) Speed remains the same
The text was updated successfully, but these errors were encountered: