I'm going to keep it brief this time  :

https://github.com/Genoil/ZECMiner (planning to keep the reade up to date on this one!)

Binaries only, sorry.

So until the big boys are ready with their 100Sol/s cannons, you can mine some ZEC with this piece of shit. Highly unstable but pretty fast thanks to @mrb's SilentArmy kernels. yay

[What is ethminer-0.9.41-genoil-1.1.x?]

What is ethminer-0.9.41-genoil-1.1.x?

Formerly known as Genoil's CUDA miner, ethminer-0.9.41-genoil-1.x.x is a fork of the stock ethminer version 0.9.41. While native CUDA support is its most significant difference, I wanted to bring some newly developed features to your attention, that are also interesting for AMD miners:

• on-GPU DAG generation
• stratum mining without proxy
• failover farm URL (getwork+stratum)
• realistic benchmarking against arbitrary epoch/DAG/blocknumber
• OpenCL devices picking
• cleaner and more useful log output

Source code: https://github.com/Genoil/cpp-ethereum
Releases: https://github.com/Genoil/cpp-ethereum/tree/master/releases


F.A.Q

1. Why is my hashrate with Nvidia cards on Windows 10 so low?
The new WDDM 2.0 driver on Windows 10 uses a different way of addressing the GPU. This is good for a lot of things, but not for ETH mining. There is a way of mining ETH at Win7/8/Linux speeds on Win10, by downgrading the GPU driver to a Win7 one (i.e 347.52) and using a special build which I will post soon. Credits to @Mo35 from the ETH forums for figuring that out.

2. And what about the GTX750Ti?
Unfortunately the issue is a bit more serious on the GTX750Ti, already causing suboptimal performance on Win7 and Linux. Apparently about 5MH/s can still be reached on Linux, which, depending on ETH price, could still be profitable, considering the extremely low power draw.

3. Are AMD cards also affected by this issue?
Only GCN 1.0 cards (HD 78x0, 79x0, R9 270, R9 280) and in a different way. While Nvidia cards have thresholds (i.e 2GB for 9x0 / Win7) of the DAG file size after which performance will drop steeply, on those AMD cards the hashrate also drops with increasing DAG size, but more in a linear pattern.

4. Can I mine ETH with my 2GB GPU?
2GB should be sufficient until Ethereum switches to PoS. I don't keep an exact list of all supported GPU's, but generally speaking the following cards should be ok:
AMD HD78xx, HD79xx, R9 2xx, R9 3xx, Fury.
Nvidia Geforce 5x0, 6x0, 7x0, 8x0, 9x0, TITAN
Quadro, Tesla & FirePro's with similar silicon should be fine too.

5. Can I buy a private kernel from you that hashes faster?
No.

6. What are the optimal launch parameters?
The default parameters are fine in most scenario's (CUDA). For OpenCL it varies a bit more. Just play around with the numbers and use powers of 2. GPU's like powers of 2.

7. Is your miner faster than the stock miner?
Yes. I don't know how much. It's more or less on par with CDM, depending on who you ask and how you measure.





 

During the development of the CUDA miner for Ethereum, I ran into an issue where the hashrate on GTX750Ti dramatically drops when the size of the memory buffer the miner operates on exceeds a certain threshold (1GB on Win7/Linux, 512MB on Win8/10). After a long discussion on the CUDA forums, one of the designers of CUDA weighed in and identified the issue as TLB trashing. I'm currently conducting a bit of research on the subject and have created a simple test program that measures these effects. It simulates the 'dagger' part of the Ethereum algorithm at different memory buffer (DAG) sizes and writes the results to a CSV file. So far, I have concluded that it is not an Nvidia-only issue, but manifests on AMD hardware as well. And apparently this is not an ETH-only issue, I've got some reports from srcypt-jane miners in as well.

I'm currently looking for as many as possible hardware/OS combinations to come to a recommendation for miners as well as designers of new algo's. Below is an example for ETH hashrate on GTX780 on Windows with increasing buffer size (in MB):



The test program can be dowloaded from https://github.com/Genoil/dagSimCL. Win-64 binaries are in the x64/Release folder. You can also build it yourself, but only have supporting MSVC files targetted at Nvidia OpenCL. On AMD hardware you may want to run

Code:

set GPU_MAX_ALLOC_PERCENT 100

first. By default, the program tries to use all of your GPU's RAM up until 4096MB. If you have less system RAM, you may add a cmd line param to test up until a lower maximum:

Code:

dagsimCL.exe 2048

If you have multiple GPU's, you need to add a second param:

Code:

dagsimCL.exe 4096 1

If you have multiple OpenCL platform installed:

Code:

dagsimCL.exe 4096 0 1

I would be very grateful if you could participate in this bit of research and possible discuss any workarounds. Thanks!

p.s. note that achieved hashrates with the test program can be significantly higher than what you actaully get with ethminer. This is because it only simautes the Dagge stages, not the Keccak stages.