Posts Tagged ‘ccMiner tpruvot


Alexis Provos has updated his fork of ccMiner (source) with improved performance for mining Vcash and Decred Blake256-based crypto coins and we have compiled a Windows binary to try it out. His latest release brings the same performance or even a slightly higher for Vcash (former Vanillacoin) as the specially optimized CUDA 6.5 Compute 3.5 release of ccMiner using the latest CUDA 7.5 and the Compute version supported by the specific GPU you have. The Decred (DCR) hashrate is also higher when compared to the latest tpruvot release that includes the optimizations submitted by pallas. Below you can find a quick comparison of the hashrate you can expect from this release on GTX 980 Ti, the archive below includes a 32-bit and 64-bit binaries compiled with CUDA 7.5 and VS2013 for Compute 2.0 – Compute 5.2 GPUs, though we have not tested how it handles on older GPUs.

Do note that the focus of the ccMiner fork from Alexis Provos is on the Blake256 algorithms and most specifically on Vcash and his release brings support for very few algorithms. There are some optimizations available for the other supported algorithms as well, so you might want to compare them as well in terms of performance. It is not a full ccMiner fork with support for all of the algorithms available in other releases, so with this one you can mine only the following algorithms:

– blake for Blake256-14rounds (SFR)
– decred for Blake256-14rounds (DCR)
– blakecoin for Blake256-8rounds (BLC)
– vcash for Blake256-8rounds (XVC)
– whirlpoolx for WhirlpoolX (old VNL algo)
– keccak for keccak256 (Maxcoin)
– lyra2 for LyraBar
– lyra2v2 for VertCoin

Since this fork is not based on the latest code by tpruvot there might be some bugs that have been resolved in the newer codebase of tpruvot’s ccMiner. We have observed something strange already, namely the very fast increase of the difficulty to a very high level on the Suprnova pool for Decred using Stratum over getwork, though it works just fine on YIIMP. In the end the difficulty issue appeared to be temporary and apparently something poolside and not related to the miner itself. Below you can find some performance comparison results using an Nvidia GTX 980 Ti GPU:

This release with GTX 980 Ti intensity 31 Decred, 30 Vcash
Vcash – 4453 MHS
Decred – 2394 MHS

1.7.4 alexis78 release Compute 3.5 CUDA 6.5
Vcash – 4418 MHS

Latest 1.7.6-git tpruvot with Pallas tweaks
Decred – 2218 MHS

To download the latest ccMiner version 1.7.1-git by alexis78 with improved performance for Windows OS…


We have compiled ccMiner 1.7.4 tpruvot’s fork Windows binary in a version with the optimal settings for mining Vanillacoin (VNL) on more recent Nvidia-based GPUs as suggested by Alexis Provos and with his performance optimizations as implemented by tpruvot in the latest code. This Windows binary is a 32-bit one compiled with CUDa 6.5 and only with Compute 3.5 support as apparently this provides the optimal performance at least on Maxwell-based Nvidia GPUs (Faster than using Compute 5.2 on them). Below you can also see a comparison that we did with Nvidia GeForce GTX 970 from Gigabyte (WF3OC) and a reference design Gigabyte GTX 980 Ti to see the difference in performance with the regular version when using CUDA 7.5 and Compute 5.2 and with the optimized CUDA 6.5 and Compute 3.5 version available for download below. Do note that although this binary will work with other algorithms as well as the Blake 256 8-rounds used by VanillaCoin it may not provide the optimal performance for other algorithms as it is targeted to provide the best VNL mining hashrate.

GeForce GTX 970 – CUDA 7.5 Compute 5.2
Default – 2490 MHS @ 164 W
Intensity 25 – 2535 MHS
Intensity 26 – 2637 MHS
Intensity 27 – 2692 MHS
Intensity 28 – 2718 MHS
Intensity 29 – 2722 MHS
Intensity 30 – 2729 MHS
Intensity 31 – 2732 MHS

GTX 980 Ti – CUDA 7.5 Compute 5.2
Default – 3390 MHS @ 211 W
Intensity 25 – 3797 MHS
Intensity 26 – 3884 MHS
Intensity 27 – 3986 MHS
Intensity 28 – 4009 MHS
Intensity 29 – 4043 MHS
Intensity 30 – 4075 MHS
Intensity 31 – 4132 MHS

GeForce GTX 970 – CUDA 6.5 Compute 3.5
Intensity 31 – 2942 MHS @ 177 W

GeForce980 – CUDA 6.5 Compute 3.5
Intensity 31 – 4418 MHS @ 238 W

Do note that increasing the intensity over the default setting (no manual -i intensity option used) even on a regular release will provide some increase in performance as you can see in our comparison going up to the maximum supported intensity of 31. Have in mind that increasing intensity also makes the system a bit less responsive the higher you go and at 30/31 it will be lagging more, but the extra performance gain you will get with the optimal binary and higher Intensity setting is significant, so for a dedicated mining rig for VanillaCoin you should definitely go for it.

Update: This particular performance optimization is for VanillaCoin’s Blake256 8-rounds implementation, the CUDA 6.5 and Compute 3.5 compilation of the particular CUDA code for that algorithm give better performance than Compute 5.0 or 5.2. The CUDA code is different for other Blake 256 algorithms, including the one for Decred’s Blake-256 14-rounds implementation, so do not expect performance increase in others. In fact specifically for Decred, a 64-bit compilation with CUDA 7.5 and for Compute 5.x does seem to provide best performance with the publicly available ccMiner 1.7.4 fork from tpruvot.

To download the ccMiner version 1.7.4 by tpruvot for VanillaCoin mining for Windows OS…


Last year we have published a quick guide to help people with Nvidia-based GPUs to go for the right fork of ccMiner based on their video card capabilities, so it is time we update that guide with the latest Nvidia GPUs. Below is a list of all of the Nvidia-based video cards and their Compute capabilities to help you figure it out depending on what video card you are using. Do note that the list does not include only the consumer Geforce series, but also Quadro and Tesla. You will find the cards that have at least Compute 2.0 capabilities as there is no way to currently make use of an older GPU than a one capable of supporting Compute 2.0 for mining with ccMiner. Furthermore you need to use a special build of ccMiner that comes with support for Compute 2.0 and 2.1 cards as the latest official builds only support Compute 3.0 or newer GPUs (not all of the more recent algorithms are supported). Below is the list of cards and their Compute capabilities you can find links for the respective versions of ccMiner to use…

Compute 2.0 video cards (Fermi – GF100, GF110):
GeForce GTX 590, GeForce GTX 580, GeForce GTX 570, GeForce GTX 480, GeForce GTX 470, GeForce GTX 465, GeForce GTX 480M, Quadro 6000, Quadro 5000, Quadro 4000, Quadro 4000 for Mac, Quadro Plex 7000, Quadro 5010M, Quadro 5000M, Tesla C2075, Tesla C2050/C2070, Tesla M2050/M2070/M2075/M2090

Compute 2.1 video cards (Fermi – GF104, GF106 GF108,GF114, GF116, GF119):
GeForce GTX 560 Ti, GeForce GTX 550 Ti, GeForce GTX 460, GeForce GTS 450, GeForce GTS 450, GeForce GT 640 (GDDR3), GeForce GT 630, GeForce GT 620, GeForce GT 610, GeForce GT 520, GeForce GT 440, GeForce GT 440, GeForce GT 430, GeForce GT 430, GeForce GTX 675M, GeForce GTX 670M, GeForce GT 635M, GeForce GT 630M, GeForce GT 625M, GeForce GT 720M, GeForce GT 620M, GeForce 710M, GeForce 610M, GeForce GTX 580M, GeForce GTX 570M, GeForce GTX 560M, GeForce GT 555M, GeForce GT 550M, GeForce GT 540M, GeForce GT 525M, GeForce GT 520MX, GeForce GT 520M, GeForce GTX 485M, GeForce GTX 470M, GeForce GTX 460M, GeForce GT 445M, GeForce GT 435M, GeForce GT 420M, GeForce GT 415M, GeForce 710M, GeForce 410M, Quadro 2000, Quadro 2000D, Quadro 600, Quadro 410, Quadro 4000M, Quadro 3000M, Quadro 2000M, Quadro 1000M, NVS 5400M, NVS 5200M, NVS 4200M

Compute 3.0 video cards (Kepler – GK104, GK106, GK107):
GeForce GTX 770, GeForce GTX 760, GeForce GT 740, GeForce GTX 690, GeForce GTX 680, GeForce GTX 670, GeForce GTX 660 Ti, GeForce GTX 660, GeForce GTX 650 Ti BOOST, GeForce GTX 650 Ti, GeForce GTX 650, GeForce GTX 780M, GeForce GTX 770M, GeForce GTX 765M, GeForce GTX 760M, GeForce GTX 680MX, GeForce GTX 680M, GeForce GTX 675MX, GeForce GTX 670MX, GeForce GTX 660M, GeForce GT 750M, GeForce GT 650M, GeForce GT 745M, GeForce GT 645M, GeForce GT 740M, GeForce GT 730M, GeForce GT 640M, GeForce GT 640M LE, GeForce GT 735M, GeForce GT 730M, Quadro K5000, Quadro K4000, Quadro K2000, Quadro K2000D, Quadro K600, Quadro K500M, Tesla K10

Compute 3.5 video cards (Kepler – GK110, GK208):
GeForce GTX TITAN Z, GeForce GTX TITAN Black, GeForce GTX TITAN, GeForce GTX 780 Ti, GeForce GTX 780, GeForce GT 640 (GDDR5), GeForce GT 630 v2, Quadro K6000, Tesla K40, Tesla K20x, Tesla K20

Compute 5.0 video cards (Maxwell – GM107, GM108):
GeForce GTX 750 Ti, GeForce GTX 750, GeForce GTX 860M, GeForce GTX 850M, GeForce 845M, GeForce 840M, GeForce 830M, GeForce GTX 960M, GeForce GTX 950M, GeForce 940M, GeForce 930M, Quadro K2200, Quadro K1200, Quadro K620, Quadro K620M

Compute 5.2 video cards (Maxwell – GM200, GM204, GM206):
GeForce GTX 960, GeForce GTX 970, GeForce GTX 980, GeForce GTX 980 Ti, GeForce GTX Titan, GeForce GTX 980M, GeForce GTX 970M, GeForce GTX 965M, Quadro M6000

Download ccMiner KBomba fork with support for older Compute 2.x GPUs
Download the latest ccMiner tpruvot fork with support for Compute 3.0 – 5.2 GPUs…
Download the latest ccMiner SP-MOD fork with support for newer Compute 5.0 and 5.2 Mxawell GPUs…