[ANN] ETHASH Miner - Eminer v0.6.1-RC2 Released (Windows, Linux, MacOS)

[peteycamey]

slightly better pool side reported hash rate and slightly higher power consumption.

very stable, and nice UI for cloud service.

intensity does not seem to make any difference.

overall 9/10.

[1714022130]

1714022130

[1714022130]

1714022130

[1714022130]

1714022130

[1714022130]

1714022130

[1714022130]

1714022130

[1714022130]

1714022130

[laik2]

slightly better pool side reported hash rate and slightly higher power consumption.

very stable, and nice UI for cloud service.

intensity does not seem to make any difference.

overall 9/10.

Sorry for the late answer.
Yes intensity doesn't make any difference as of power usage, but it does reduce hashrate.

[E-Miner]

any update soon?

I'm working for new update, I will announce soon.

You're doing better with keeping your IP hard(er) to get at - nice work. Might want to use C instead of Go so you can put in some anti-debugging traps, too.

Also... in your "Optimized 4 threads" OpenCL... I know this won't make a huge difference, but it still makes me sad:

Code:

bool update_share = thread_id == ((a >> 3) % THREADS);

Were that interpreted how you wrote it (verbatim), you would be eating... 4 clocks for the shift, and an untold number of clocks for the modulo, as AMD GCN doesn't even have modulo implemented - it's emulated. In reality, it's going to optimize that to an AND, making it look more like this:

Code:

bool update_share = thread_id == ((a >> 3) & (THREADS - 1))

Okay, that's 8 clocks - two full-rate instructions. Unless you use a local worksize that's not a power of two, and in that case, god help you. But we can do better.

First, for AMD - you're using LDS. Any worksize above wavefront size (64 work-items) is going to make those barriers take a LOT longer. Reason being, an AMD GCN CU (Compute Unit) only executes wavefronts. Larger work groupings are cut into wavefront-sized pieces and executed that way. If you use an LDS barrier with a worksize of 64 (wavefront size) - big deal, the whole wavefront is handled by that CU, and as such, the barriers can actually be omitted! And they are, by the AMD OCL compiler, in that case. When you make your group larger - suddenly you need to sync with other execution units: this is going to make you very sad. So - at least for AMD - I would keep it to 64 work-items/local group.

Now - we know the value of THREADS - the kernel says it's a 4-way - so... get you one of these...

Code:

#pragma OPENCL EXTENSION cl_amd_media_ops2 : enable

... and suddenly you have access to the amd_bfe builtin, which is purpose-built for what you wanna do! It gives you direct access to the v_alignbit_b32 instruction. And this gives us:

Code:

bool update_share = thread_id == amd_bfe(a, 3U, 2U);

Shaving at LEAST four ticks off the best the compiler would likely come up with (and I am being generous.) As it's looped, this magnifies the effect of the optimization, although it's still not much. Now you have the operation done in a single full-rate instruction, though - which IS an improvement.

WOW! tons of job like for me. @Wolf thanks your mention. I'll keep up these and will be share results here.

[fr4nkthetank]

w0lf is a legend.  Always ready to help others, although he won't spoon feed you but when people want to learn i've seen him time and time again help out and spread the knowledge.  If only we had more wolfs in crypto and less sp's   I'll test out your new update when you get it out

[terrxysq]

it does seem that sometimes the miner would just stop working solutions but would not crash. the error handling and watchdog feature need to be improved. wonder when will there be a new version coming out?

[smparo]

Last days I notice that the software some times not report to the mining pool the stale share that I can view on the console
The problem that I had was low shares and for testing I started claymore miner and I notice that I found a lot of stale shares: it's okay ... the pool have some problems!   
Now the problem is away but can you correct this problem?

[smparo]

I forgot:
with claymore miner I saw all stale shares on the mining pool (claymore console stale shares=mining pool stale shares)
with eminer I saw few stale shares on the pool although I saw all on the console (eminer console stale shares>mining pool stale shares)
Just to clarify...

Great job and great miner anyway!!! 

[doktor83]

w0lf is a legend.  Always ready to help others, although he won't spoon feed you but when people want to learn i've seen him time and time again help out and spread the knowledge.  If only we had more wolfs in crypto and less sp's   I'll test out your new update when you get it out

Depends on his mood, sometimes really generous and helpful, and sometimes only bragging 

[fr4nkthetank]

w0lf is a legend.  Always ready to help others, although he won't spoon feed you but when people want to learn i've seen him time and time again help out and spread the knowledge.  If only we had more wolfs in crypto and less sp's   I'll test out your new update when you get it out

Depends on his mood, sometimes really generous and helpful, and sometimes only bragging 

hahahahaha for sure, and be warned if you ever click on one of his image links.  Be very warned

[thehero18]

any plans for dual mining?

[doktor83]

w0lf is a legend.  Always ready to help others, although he won't spoon feed you but when people want to learn i've seen him time and time again help out and spread the knowledge.  If only we had more wolfs in crypto and less sp's   I'll test out your new update when you get it out

Depends on his mood, sometimes really generous and helpful, and sometimes only bragging 

hahahahaha for sure, and be warned if you ever click on one of his image links.  Be very warned

sexual content, yeah i know
foxes and stuff

[Victorio]

E-Miner,
How often does the devfee instance run and what coin does it mine?
I am looking to use Eminer rather than Claymore on new Ethash forks and DAG switching matters.

[tyoma]

E-Miner,
How often does the devfee instance run and what coin does it mine?
I am looking to use Eminer rather than Claymore on new Ethash forks and DAG switching matters.

You can choose coin in what devfee mine.

[jeswin]

Seems interesting, definitely will have a look 

[terrxysq]

is development on this miner stopped?

[phuocduong]

who compare with claymore?

[flat1983]

I like  but but

[E-Miner]

is development on this miner stopped?

Development continue. I will announce new version soon.

[smparo]

who compare with claymore?

On AMD Rx580 I have done some compare with claymore and for me on mono mining the winner is eminer: the reported share on the pool is very close to share reported from eminer.
I have two RX580 (GPU 1150MHz - memory 2175MHz), with eminer i go to 61.2Mh/s while with claymore I have 61.4Mh/s
On the pool the effective hashrate with eminer is from 57.8 to 59.8Mh/s (rarely also 60.1Mh/s!!!!) while with claymore is from 57 to only 58Mh/s ( )

I do not know why this happens but for now I prefer to use eminer!

Claymore has its merits in other peculiarities see the possibility of configuring Mhz and mV

[smparo]

is development on this miner stopped?

Development continue. I will announce new version soon.

When you will release the new version? Soon = just some days from now or weeks?
Please keep us up to date