All About BTC, LTC, ETH mining as well as other alternative crypto currencies
Time for another group of tests of the newly released GeForce GTX 1080 Ti Founders Edition video card by Nvidia. This time we have used the latest released of the ccMiner 2.0 RC2 fork by Tpruvot in order to test how all of the supported algorithms perform on the new GPU. Do note that not all of the supported crypto algorithms by this miner may be performing the fastest, so you should use the results as a reference if comparing results from 2.0 RC2 release only. We have managed to successfully test the hashrate on most of the supported algorithms by this miner, though we still did have trouble making some of them work, but that is to be expected with a new GPU release…
We have used ccMiner 2.0 RC2 by tpruvot in benchmark mode with all of the default settings for intensity on all algorithms supported by the miner. The GeForce GTX 1080 Ti GPU was running at the default 100% TDP or with other words a Power Limiter at 250W, though on the Founders Edition GPUs you can increase it by up to 20% all the way to 300W (mind the cooling though). The tests were performed on stock operating frequencies of the video card with the fan set at 100% in order to keep the GPU cool and prevent thermal throttling (dropping of the boost frequency) because of high temperature that might be reached with auto fans.
As you can see in the table with performance results above we have posted the hashrate and the power usage for each algorithm tested (if the test has successfully passed). The power usage values are the ones reported by the video card itself only and are based on its TDP limit, not the actual values measured at the wall (these will be higher). The algorithms pushing the 250W TDP limit might be able to benefit from a power limit increase, though you might want to be careful with that in terms of being able to properly cool down the card. On the other hand forcing the TDP limited down might bring significant power reduction with a little sacrifice in terms of hashrate thus giving you better performance per Watt than the stock settings.
With the BMW algorithm we got an error at the default intensity of 21, and we’ve had to decrease it down to 15 in order to make it work, resulting in very low hashrate. With Cryptonight we got an error at the default intensity of 10.75, but down to 10.25 it worked and you can see the result in the table. With the Jackpot algorithm we also got an error at the default intensity of 20, however lowering it did not seem to help at all and the same thing also applies to the Quark algorithm. With the Wildkeccak algorithm we had trouble making it work properly in benchmark mode due to the specifics of the algorithm needing a scratchpad file.
The development of some of the ccMiner forks for Nvidia GPU miners didn’t seem very active visually in the last couple of months, especially with coins such as ZCash (ZEC) that came with their own miner releases, but it hasn’t been stopped. A few days ago tpruvot has made a pre-release version of his new ccMiner 2.0 available (source) for people interested in checking it out with probably a few small things left to be ironed out before the final 2.0 release is made available. So if you are using Nvidia GPUs to mine crypto coins then you might want to give it a try and don’t forget to send a tip to your local friendly ccMiner developer for a beer or two to show your support.
ccMiner 2.0 RC2 changelog:
– Handle cryptonight, wildkeccak and cryptonight-lite
– Add a series of new algorithms: timetravel, bastion, hmq1725, sha256t
– Import lyra2z from djm34 work…
– Rework the common skein512 (used in most algos except skein ;)
– Upgrade whirlpool algo with alexis version (2x faster)
– Store the share diff of second nonce(s) in most algos
– Hardware monitoring thread to get more accurate power readings
– Small changes for the quiet mode & max-log-rate to reduce logs noise
– Blake2s fix, variant built with CUDA 6.5 (not usable for lbry)
Do note that this release may not contain the best optimizations and fastest performance on all of the supported algorithms, so depending on what you are currently mining you may need to stick to another faster fork of ccMiner or not. Also the CUDA 6.5 binary release does not work for LBRY mining as noted in the changelog, so either use the 8.0 release or compile with 7.5 for mining that coin.
The recent addition of the X11-Gost algorithm on NiceHash that is being used by SIBCoin (SIB) has increased the user interest in the coin and the algorithm as expected. NiceHash has recommended the use of the latest release of ccMiner by tpruvot for X11-Gost support on their servers, but it seems that this is not the fastest solution available to Nvidia miners as was pointed out to us. While ccminer v1.8.4 from tpruvot does about 8 MHs on a stock GTX 1070 GPU, but you can get faster speeds on the same hardware by using the latest ccMiner fork from alexis 78 (source). We have compiled a 64-bit Windows binary with Compute 5.x support and CUDA 7.5 for Nvidia Maxwell GPUs from the latest source for mining X11-Gost (SIBCoin) and with it you can get about 10-11 MHs on a stock GTX 1070 GPU.
Do note that on mining rigs with multiple GPUs you might need to increase the amount of virtual memory (SWAP file) if you have less system memory in order to be able to run the miner with the default high intensity. On a 6x GTX 1070 GPUs mining rig with 8GB RAM we’ve had to increase the virtual memory to 24GB in order to be able to run the miner properly at the default intensity of 22 set for the X11-Gost algorithm in the miner, otherwise the miner just crashes… 8GB RAM and 20GB SWAP file was not enough apparently.