Crypto Mining Blog
It Is All About BTC, LTC, ETH, DOGE, KAS mining as well as other alternative crypto currencies
Search
Search Results
The latest release of the ccMiner 1.7 fork by tpruvot (source) has added some new interesting functionality among which is the ability to run a benchmark on all of the supported crypto algorithms by the software. There is no more need to go through all of the algorithms one by one and record the returned results, all you have to do is run ccminer.exe --benchmark and the miner will go through all of the algorithms automatically and print out the hashrate you get with your particular Nvidia GPU. It can work with single and multiple GPUs in the system, but if you have more than one and you do not specify which one you want tested it will benchmark all of them and display individual hashrate. Thanks to the ease of use of this feature and the fact that it needs just about 5 minutes to run we might soon start seeing crypto hashrate benchmarks included in Nvidia GPU reviews on sites that do hardware reviews, but generally do not bother to test crypto mining performance.
Since the output in the console when you run ccMiner in benchmark mode is quite big, you might want to automate the run and have the results written to a text file by default that you can later open and view more easily than having to scroll in a console window. To do so and have the results written to benchmark.txt file just run the following command line: ccminer.exe --benchmark > benchmark.txt
Here is a sample benchmark run on a GTX 980 Ti GPU:
*** ccminer 1.7 for nVidia GPUs by tpruvot@github ***
Built with VC++ 2013 and nVidia CUDA SDK 6.5Originally based on Christian Buchner and Christian H. project
Include some of the work of djm34, sp, tsiv and klausT.BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)
[2015-11-07 14:08:41] Starting benchmark mode with blakecoin
[2015-11-07 14:08:41] NVAPI GPU monitoring enabled.
[2015-11-07 14:08:41] 1 miner thread started, using 'blakecoin' algorithm.
[2015-11-07 14:08:44] GPU #0: GeForce GTX 980 Ti, 1503.75 MH/s
[2015-11-07 14:08:47] GPU #0: GeForce GTX 980 Ti, 1485.03 MH/s
[2015-11-07 14:08:47] GPU #0: blakecoin hashrate = 1494.39 MH/s
[2015-11-07 14:08:47] Benchmark algo blake...
[2015-11-07 14:08:51] GPU #0: GeForce GTX 980 Ti, 997.23 MH/s
[2015-11-07 14:08:56] GPU #0: GeForce GTX 980 Ti, 990.02 MH/s
[2015-11-07 14:08:56] GPU #0: blake hashrate = 993.62 MH/s
[2015-11-07 14:08:56] Benchmark algo bmw...
[2015-11-07 14:08:58] GPU #0: GeForce GTX 980 Ti, 1384.80 MH/s
[2015-11-07 14:09:02] GPU #0: GeForce GTX 980 Ti, 1389.88 MH/s
[2015-11-07 14:09:02] GPU #0: bmw hashrate = 1387.34 MH/s
[2015-11-07 14:09:03] Benchmark algo deep...
[2015-11-07 14:09:12] GPU #0: GeForce GTX 980 Ti, 32.92 MH/s
[2015-11-07 14:09:21] GPU #0: GeForce GTX 980 Ti, 32.93 MH/s
[2015-11-07 14:09:22] GPU #0: deep hashrate = 32.93 MH/s
[2015-11-07 14:09:22] Benchmark algo fresh...
[2015-11-07 14:09:28] GPU #0: GeForce GTX 980 Ti, 12.02 MH/s
[2015-11-07 14:09:32] GPU #0: GeForce GTX 980 Ti, 12.03 MH/s
[2015-11-07 14:09:32] GPU #0: fresh hashrate = 12.03 MH/s
[2015-11-07 14:09:32] Benchmark algo fugue256...
[2015-11-07 14:09:34] GPU #0: GeForce GTX 980 Ti, 373.83 MH/s
[2015-11-07 14:09:42] GPU #0: GeForce GTX 980 Ti, 376.02 MH/s
[2015-11-07 14:09:42] GPU #0: fugue256 hashrate = 376.02 MH/s
[2015-11-07 14:09:42] Benchmark algo groestl...
[2015-11-07 14:09:45] GPU #0: GeForce GTX 980 Ti, 30.83 MH/s
[2015-11-07 14:09:55] GPU #0: GeForce GTX 980 Ti, 30.76 MH/s
[2015-11-07 14:09:55] GPU #0: groestl hashrate = 30.80 MH/s
[2015-11-07 14:09:56] Benchmark algo heavy...
[2015-11-07 14:10:02] GPU #0: GeForce GTX 980 Ti, 30.82 MH/s
[2015-11-07 14:10:05] GPU #0: GeForce GTX 980 Ti, 30.86 MH/s
[2015-11-07 14:10:05] GPU #0: heavy hashrate = 30.84 MH/s
[2015-11-07 14:10:05] Benchmark algo keccak...
[2015-11-07 14:10:10] GPU #0: GeForce GTX 980 Ti, 347.10 MH/s
[2015-11-07 14:10:15] GPU #0: GeForce GTX 980 Ti, 394.14 MH/s
[2015-11-07 14:10:15] GPU #0: keccak hashrate = 394.14 MH/s
[2015-11-07 14:10:15] Benchmark algo jackpot...
[2015-11-07 14:10:20] GPU #0: GeForce GTX 980 Ti, 6292.92 kH/s
[2015-11-07 14:10:22] GPU #0: GeForce GTX 980 Ti, 6595.98 kH/s
[2015-11-07 14:10:22] GPU #0: jackpot hashrate = 6444.45 kH/s
[2015-11-07 14:10:23] Benchmark algo luffa...
[2015-11-07 14:10:23] GPU #0: GeForce GTX 980 Ti, 111.07 MH/s
[2015-11-07 14:10:23] GPU #0: GeForce GTX 980 Ti, 6572.03 MH/s
[2015-11-07 14:10:27] GPU #0: luffa hashrate = 6572.03 MH/s
[2015-11-07 14:10:27] Benchmark algo lyra2...
[2015-11-07 14:10:32] GPU #0: GeForce GTX 980 Ti, 1078.98 kH/s
[2015-11-07 14:10:33] GPU #0: GeForce GTX 980 Ti, 1119.20 kH/s
[2015-11-07 14:10:33] GPU #0: lyra2 hashrate = 1099.09 kH/s
[2015-11-07 14:10:34] Benchmark algo lyra2v2...
[2015-11-07 14:10:39] GPU #0: GeForce GTX 980 Ti, 9949.18 kH/s
[2015-11-07 14:10:42] GPU #0: GeForce GTX 980 Ti, 12.46 MH/s
[2015-11-07 14:10:42] GPU #0: lyra2v2 hashrate = 12.46 MH/s
[2015-11-07 14:10:43] Benchmark algo myr-gr...
[2015-11-07 14:10:53] GPU #0: GeForce GTX 980 Ti, 43.80 MH/s
[2015-11-07 14:11:03] GPU #0: GeForce GTX 980 Ti, 43.67 MH/s
[2015-11-07 14:11:03] GPU #0: myr-gr hashrate = 43.73 MH/s
[2015-11-07 14:11:03] Benchmark algo neoscrypt...
[2015-11-07 14:11:03] GPU #0: Using 8192 cuda threads
[2015-11-07 14:11:13] GPU #0: GeForce GTX 980 Ti, 660.65 kH/s
[2015-11-07 14:11:23] GPU #0: GeForce GTX 980 Ti, 661.27 kH/s
[2015-11-07 14:11:23] GPU #0: neoscrypt hashrate = 660.96 kH/s
[2015-11-07 14:11:23] Benchmark algo nist5...
[2015-11-07 14:11:31] GPU #0: GeForce GTX 980 Ti, 20.42 MH/s
[2015-11-07 14:11:33] GPU #0: GeForce GTX 980 Ti, 23.67 MH/s
[2015-11-07 14:11:33] GPU #0: nist5 hashrate = 22.04 MH/s
[2015-11-07 14:11:33] Benchmark algo penta...
[2015-11-07 14:11:41] GPU #0: GeForce GTX 980 Ti, 12.11 MH/s
[2015-11-07 14:11:42] GPU #0: GeForce GTX 980 Ti, 15.95 MH/s
[2015-11-07 14:11:42] GPU #0: penta hashrate = 14.03 MH/s
[2015-11-07 14:11:43] Benchmark algo quark...
[2015-11-07 14:11:47] GPU #0: GeForce GTX 980 Ti, 14.64 MH/s
[2015-11-07 14:11:49] GPU #0: GeForce GTX 980 Ti, 15.42 MH/s
[2015-11-07 14:11:49] GPU #0: quark hashrate = 15.03 MH/s
[2015-11-07 14:11:50] Benchmark algo qubit...
[2015-11-07 14:11:52] GPU #0: GeForce GTX 980 Ti, 15.95 MH/s
[2015-11-07 14:11:53] GPU #0: GeForce GTX 980 Ti, 15.82 MH/s
[2015-11-07 14:11:53] GPU #0: qubit hashrate = 15.82 MH/s
[2015-11-07 14:11:53] Benchmark algo skein...
[2015-11-07 14:11:58] GPU #0: GeForce GTX 980 Ti, 332.57 MH/s
[2015-11-07 14:12:01] GPU #0: GeForce GTX 980 Ti, 330.01 MH/s
[2015-11-07 14:12:01] GPU #0: skein hashrate = 331.29 MH/s
[2015-11-07 14:12:02] Benchmark algo skein2...
[2015-11-07 14:12:05] GPU #0: GeForce GTX 980 Ti, 85.98 MH/s
[2015-11-07 14:12:07] GPU #0: GeForce GTX 980 Ti, 219.13 MH/s
[2015-11-07 14:12:07] GPU #0: skein2 hashrate = 219.13 MH/s
[2015-11-07 14:12:07] Benchmark algo s3...
[2015-11-07 14:12:08] GPU #0: GeForce GTX 980 Ti, 28.61 MH/s
[2015-11-07 14:12:17] GPU #0: GeForce GTX 980 Ti, 29.49 MH/s
[2015-11-07 14:12:17] GPU #0: s3 hashrate = 29.49 MH/s
[2015-11-07 14:12:18] Benchmark algo x11...
[2015-11-07 14:12:24] GPU #0: GeForce GTX 980 Ti, 9270.83 kH/s
[2015-11-07 14:12:29] GPU #0: GeForce GTX 980 Ti, 9906.28 kH/s
[2015-11-07 14:12:29] GPU #0: x11 hashrate = 9906.28 kH/s
[2015-11-07 14:12:29] Benchmark algo x13...
[2015-11-07 14:12:38] GPU #0: GeForce GTX 980 Ti, 8304.47 kH/s
[2015-11-07 14:12:39] GPU #0: GeForce GTX 980 Ti, 8229.94 kH/s
[2015-11-07 14:12:39] GPU #0: x13 hashrate = 8267.20 kH/s
[2015-11-07 14:12:39] Benchmark algo x14...
[2015-11-07 14:12:48] GPU #0: GeForce GTX 980 Ti, 8275.62 kH/s
[2015-11-07 14:12:49] GPU #0: GeForce GTX 980 Ti, 8168.95 kH/s
[2015-11-07 14:12:49] GPU #0: x14 hashrate = 8222.28 kH/s
[2015-11-07 14:12:49] Benchmark algo x15...
[2015-11-07 14:12:58] GPU #0: GeForce GTX 980 Ti, 7292.03 kH/s
[2015-11-07 14:12:59] GPU #0: GeForce GTX 980 Ti, 7233.74 kH/s
[2015-11-07 14:12:59] GPU #0: x15 hashrate = 7262.88 kH/s
[2015-11-07 14:13:00] Benchmark algo x17...
[2015-11-07 14:13:06] GPU #0: GeForce GTX 980 Ti, 6703.77 kH/s
[2015-11-07 14:13:09] GPU #0: GeForce GTX 980 Ti, 6650.18 kH/s
[2015-11-07 14:13:10] GPU #0: x17 hashrate = 6676.98 kH/s
[2015-11-07 14:13:10] Benchmark algo whirlpool...
[2015-11-07 14:13:18] GPU #0: GeForce GTX 980 Ti, 17.52 MH/s
[2015-11-07 14:13:19] GPU #0: GeForce GTX 980 Ti, 17.41 MH/s
[2015-11-07 14:13:19] GPU #0: whirlpool hashrate = 17.47 MH/s
[2015-11-07 14:13:20] Benchmark algo whirlpoolx...
[2015-11-07 14:13:26] GPU #0: GeForce GTX 980 Ti, 250.26 MH/s
[2015-11-07 14:13:36] GPU #0: GeForce GTX 980 Ti, 251.12 MH/s
[2015-11-07 14:13:36] GPU #0: whirlpoolx hashrate = 250.69 MH/s
[2015-11-07 14:13:37] Benchmark algo zr5...
[2015-11-07 14:13:46] GPU #0: GeForce GTX 980 Ti, 1907.64 kH/s
[2015-11-07 14:13:55] GPU #0: GeForce GTX 980 Ti, 2107.89 kH/s
[2015-11-07 14:13:55] GPU #0: zr5 hashrate = 2007.77 kH/s
[2015-11-07 14:13:55] Benchmark results for GPU #0 - GeForce GTX 980 Ti:
[2015-11-07 14:13:55] blakecoin : 1459369.4 kH/s, 1 MB, 4194304 thr.
[2015-11-07 14:13:55] blake : 970336.8 kH/s, 1 MB, 4194304 thr.
[2015-11-07 14:13:55] bmw : 1354822.5 kH/s, 65 MB, 2097152 thr.
[2015-11-07 14:13:55] deep : 32154.5 kH/s, 33 MB, 524288 thr.
[2015-11-07 14:13:55] fresh : 11745.7 kH/s, 609 MB, 524288 thr.
[2015-11-07 14:13:55] fugue256 : 367203.5 kH/s, 129 MB, 4194304 thr.
[2015-11-07 14:13:55] groestl : 30076.7 kH/s, 1 MB, 524288 thr.
[2015-11-07 14:13:55] heavy : 30115.6 kH/s, 147 MB, 524032 thr.
[2015-11-07 14:13:55] keccak : 384901.8 kH/s, 129 MB, 2097152 thr.
[2015-11-07 14:13:55] jackpot : 6293.4 kH/s, 106 MB, 1048576 thr.
[2015-11-07 14:13:55] luffa : 6417996.4 kH/s, 129 MB, 2097152 thr.
[2015-11-07 14:13:55] lyra2 : 1073.3 kH/s, 515 MB, 65536 thr.
[2015-11-07 14:13:55] lyra2v2 : 12163.3 kH/s, 393 MB, 262144 thr.
[2015-11-07 14:13:55] myr-gr : 42708.4 kH/s, 9 MB, 131072 thr.
[2015-11-07 14:13:55] neoscrypt : 645.5 kH/s, 261 MB, 8192 thr.
[2015-11-07 14:13:55] nist5 : 21525.5 kH/s, 65 MB, 1048576 thr.
[2015-11-07 14:13:55] penta : 13701.2 kH/s, 33 MB, 524288 thr.
[2015-11-07 14:13:55] quark : 14678.7 kH/s, 86 MB, 1048576 thr.
[2015-11-07 14:13:55] qubit : 15453.1 kH/s, 609 MB, 524288 thr.
[2015-11-07 14:13:55] skein : 323525.3 kH/s, 1 MB, 1048576 thr.
[2015-11-07 14:13:55] skein2 : 213998.6 kH/s, 33 MB, 524288 thr.
[2015-11-07 14:13:55] s3 : 28802.4 kH/s, 609 MB, 524288 thr.
[2015-11-07 14:13:55] x11 : 9674.1 kH/s, 609 MB, 524288 thr.
[2015-11-07 14:13:55] x13 : 8073.4 kH/s, 609 MB, 524288 thr.
[2015-11-07 14:13:55] x14 : 8029.6 kH/s, 609 MB, 524288 thr.
[2015-11-07 14:13:55] x15 : 7092.7 kH/s, 609 MB, 524288 thr.
[2015-11-07 14:13:55] x17 : 6520.5 kH/s, 609 MB, 524288 thr.
[2015-11-07 14:13:55] whirlpool : 17056.7 kH/s, 33 MB, 524288 thr.
[2015-11-07 14:13:55] whirlpoolx : 244812.1 kH/s, 65 MB, 1048576 thr.
[2015-11-07 14:13:55] zr5 : 1960.7 kH/s, 84 MB, 262144 thr.
Quick Guide on Solo GPU Mining Ethereum on Windows
14, Aug 2015
AS requested here comes a simple guide on how to solo mine Ethereum Ether coins on a local system or within a network with multiple mining rigs. Note that at this point it is already pointless to try local solo mining with CPU only, and if you do not have enough GPU power available and you end up with some bad luck you may not be able to solve a block in a long time. Also our experience shows that geth may lockup at times when solo mining not sending new work from the current block, so do monitor your mining rigs carefully should you decide to try it. If you want to mine in a pool, then you might want to check out our other Quick Guide on How to Mine Ethereum on Windows. Before you get started you need to download the geth and ethminer Windows binaries from the link below, then just follow the instructions below:
Generating wallet address:
– Open the geth folder and rungeth-console.batto start Ethereum in console mode
– The software will need to download the blockchain data, it can take some time
– In the console type:personal.newAccount("password")
– Instead of password in the quotes above write your own password and remember it well
– In the console type:eth.accounts
– This will list your Ethereum wallet address
– To check your account balance you can type:web3.fromWei(eth.getBalance(eth.coinbase), "ether")
Sending Ether to another wallet:
– First you need to unlock your account by typing in the console the following (replace password with your password):personal.unlockAccount(eth.accounts[0], "password")
– In the console type:eth.sendTransaction({from: 'your_address', to: 'recipient_address', value: web3.toWei(1, "ether")})
– In the above code replace your_address and recipient_address with the respective addresses, the example is for sending 1 Ether, but you can change the value depending on your needs
Starting geth for solo mining:
– To listen for connections only on the local system type:geth --rpc --rpcaddr "localhost" --rpcport 8545
– To be accessible on the local network type:geth --rpc --rpcaddr "192.168.0.123" --rpcport 8545
– Make sure that for local LAN accessibility you replace the rpcaddr IP address to the one that of the machine geth is running on, the 192.168.0.123 is just an example
– To be accessible on the Internet type:geth --rpc --rpcaddr "x.x.x.x" --rpcport 8545
– Make sure that for Internet accessibility you replace the rpcaddr IP address to the one that of the machine geth is running on, the x.x.x.x in the example will not work, also make sure that the 8545 port (or another one you decide to use) is forwarded
Starting ethminer for solo mining:
– For local system mining with ethminer on the same PC that geth is running on use:ethminer -G
– For mining on a system in the Local LAN where geth is installed and running use:ethminer -G -F http://192.168.0.123:8545
– Make sure that for local LAN mining the IP address of the system geth is running on is set correctly on the miner, the 192.168.0.123 is just an example, also make sure that there is no Firewall blocking connections
– For using mining rig to mine over the Internet on a PC with geth running in your local LAN use:ethminer -G -F http://x.x.x.x:8545
– For Internet access make sure that instead of the x.x.x.x in the example you set your external IP address and that the 8545 port is properly forwarded between the external IP and the system running geth
It seems that ethpool has just stopped accepting new users due to high load on their server, they have posted the following message: “Due too the high hashrate the pool currently does not accept new miners!”. So if you still haven’t started mining there, existing users can continue using the service, so now may just be the right time to try out solo mining.
– Download geth and ethminer compiled for Windows and ready to be used…
- In: Crypto Coins
- Tags: ETH solo mining, Ether, Ether CPU mining, Ether GPU mining, Ether mining, Ether solo mining, Ethereum, Ethereum CPU miner, Ethereum CUDA miner, Ethereum Frontier, Ethereum GPU miner, Ethereum miner, Ethereum mining, Ethereum mining guide, Ethereum OpenCL miner, Ethereum pool mining, Ethereum solo mining, ethminer, Ethpool, geth, solo mining
Mining with a 8X GPU GeForce GTX TITAN X System
21, Jul 2015
Here is something interesting that is not originally intended to be used as a GPU mining rig, but for a powerful compute oriented machine – an 8x GPU AsRock Rack Barebone populated with eight Nvidia GeForce GTX TITAN X video cards and two 14-core Intel Xeon processors. These powerful rackmount systems are designed for use with Nvidia Tesla cards for high-performance CUDA applications, but you can put in GeForce cards as well such as the TITAN X and have them all running at PCI-E 3.0 x16 speeds (no SLI support is available).
So we took one of these interesting systems and ran a quick test with the latest ccMiner to see what kind of performance we are going to get for crypto currency mining. It was out of curiosity as the system is not intended to be used for GPU mining – the whole things is just way too expensive to probably ever see ROI let alone make some profit from mining. Interestingly enough the 8x GPU configuration requires the use of Windows Server or compatible Linux distribution, with Windows 7 or 8.x we were having trouble making all 8 GPUs work properly (Error code 43 on the 8th card). Apparently there is a solution to make all 8 cards work fine under these consumer versions of Windows as well, all you need to do is some registry modification and you should be fine.
As you can see from the screenshot the system runs fine with a total hashrate of about 190 MHS mining Quark (98 MHS total on X11 and 25MHS total on Lyra2RE) on all eight GeForce GTX TITAN X GPUs. This means that a single TITAN X card gets you about 24 MHS for mining Quark-based crypto currencies and ll of the cards manage to provide optimum performance. Notice that the fans are turned all the way to 100% for best performance, because otherwise the cards are easily hitting the thermal limit with their fans running on auto at about 50-60% and as a result they throttle down and you loose performance with the GPU frequency dropping down to 1000 MHz. Again this is not a system designed for crypto currency mining, but for compute applications, we were just curious how well it will perform for crypto mining and it does a great job with some tweaking. Of course since the whole thing is designed to be in a server room the noise level is not relevant, though it is quite high as expected thanks to the 8 GPU fans and the other 8 chassis cooling fans that are 24W each when running at maximum RPM.
Maybe if GPU mining picks up to a large scale level like it is happening with Bitcoin mining and is profitable enough we might be able to see solutions like these used, but for now these are limited to businesses using them for high-performance CUDA applications. Think along the lines of 3D design, visual effects rendering, medical imaging, energy exploration or scientific simulations etc.