The reason is memory accessing/caching. When all GPU threads are accessing memory by random addresses at the same time it causes some overload. When some threads are busy with Decred and don't access memory, overload is less and other threads can get required data a bit faster. Because there is no way to freeze some threads I cannot use this behaviour to improve mining speed in Ethereum-only mode.
[/quote]

Thanks for the answer, is this mean that lowering number of threads will increase the eth speed?

Nice, this works:

echo '{"id":0,"jsonrpc":"2.0","method":"miner_getstat1"}' | nc localhost 3333

this dumps the raw json output so it can easily be used in a bash script in linux to do fun things

Claymore - Your miner works great on pools, a week with no issues or crashes. I am trying to setup solo mining. Have Geth running on a local LAN machine and tried to point miner from same machine as well as another LAN machine.

Used
EthDcrMiner64.exe -epool http://localhost:8545

Connects, looks like it starts mining and Geth console shows the connection. But not seeing any shares? only temps and new jobs. On pool, i'm seeing accepted shares almost instantly. Doing something wrong here?

Also, when I point another rig to my local Geth using LAN IP and same port, can't connect. Port is open, no FW running and its local LAN.


ETH: 05/19/16-17:43:38 - New job (target 0x000000000006f68d) from localhost:8545
ETH - Total Speed: 122.037 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:06
ETH: GPU0 30.444 Mh/s, GPU1 30.541 Mh/s, GPU2 30.526 Mh/s, GPU3 30.527 Mh/s
ETH: 05/19/16-17:43:43 - New job (target 0x000000000006f5af) from localhost:8545
ETH - Total Speed: 122.052 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:06
ETH: GPU0 30.473 Mh/s, GPU1 30.543 Mh/s, GPU2 30.528 Mh/s, GPU3 30.508 Mh/s
GPU0 t=63C fan=0%, GPU1 t=62C fan=0%, GPU2 t=62C fan=0%
ETH: 05/19/16-17:44:09 - New job (target 0x000000000006f68d) from localhost:8545
ETH - Total Speed: 122.006 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:06
ETH: GPU0 30.431 Mh/s, GPU1 30.532 Mh/s, GPU2 30.521 Mh/s, GPU3 30.523 Mh/s
ETH: 05/19/16-17:44:10 - New job (target 0x000000000006f5af) from localhost:8545
ETH - Total Speed: 121.798 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:06
ETH: GPU0 30.477 Mh/s, GPU1 30.533 Mh/s, GPU2 30.280 Mh/s, GPU3 30.508 Mh/s
ETH: 05/19/16-17:44:12 - New job (target 0x000000000006f4d0) from localhost:8545
ETH - Total Speed: 122.068 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:06
ETH: GPU0 30.477 Mh/s, GPU1 30.537 Mh/s, GPU2 30.539 Mh/s, GPU3 30.515 Mh/s
ETH: 05/19/16-17:44:16 - New job (target 0x000000000006f3f2) from localhost:8545
ETH - Total Speed: 122.117 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:06
ETH: GPU0 30.530 Mh/s, GPU1 30.527 Mh/s, GPU2 30.539 Mh/s, GPU3 30.521 Mh/s
GPU0 t=64C fan=0%, GPU1 t=62C fan=0%, GPU2 t=63C fan=0%
ETH: 05/19/16-17:44:43 - New job (target 0x000000000006f4d0) from localhost:8545
ETH - Total Speed: 122.040 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:07
ETH: GPU0 30.482 Mh/s, GPU1 30.519 Mh/s, GPU2 30.523 Mh/s, GPU3 30.517 Mh/s

Shares are your contributions in pool mining, so no shares in solo mining, you mine the whole thing alone. Try launching geth with --rpc --rpcaddr 192.168.x.x --farm 192.168.x.x where 192.168.x.x is the lan address of the machine running geth. For me it does work like that. With 127.0.0.1 machines in the lan can't connect.

So does the miner stop mining when a new block is found or only when its submitting a share?

You should read the theory of pool operation to understand the whole thing.

A miner calculates a "checksum" of data in the block using some hashing algorithm. The result is a very long number. To solve a block this number must be lesser than some value called target. Target depends on the speed of finding blocks by the whole network and adapts so the average rate of new blocks is constant regardless of number of miners in the network. That is, more miners - more hashpower - lesser target - harder to find a block solution.

When you mine with a pool, pool sets target for miners much higher than actual target for the block solution. So miners with low hash rates can find at least something in reasonable time frame. Those solutions are called "shares" because they do NOT solve a block. But pool can estimate miner hashrate by the rate of submitted shares. Finally some share from some miner will be smaller than a block solution. This share will solve the block, but usually miner does not know that it was its share (some pools like suprnova and pool.mn report block founders, though, for stats).

Now compare the typical target from a pool: 0x0000000112e0be82 (4611686018) with your target 0x000000000006f3f2 (455666).  4611686018/455666 ~= 10120. This means that in solo mode only 1 of 10120 such pool shares will solve a block. If your miner finds 100 shares per hour, you need 101 hour to find a solution in solo mode. Until that you will not see any shares in solo mode. You see only block solution.

Hi i have problem. I have GPU R9 280X and R9 290X in one motherboard with Windows 8, CPU 4core, 8gb ram. Here i have driver 15.12. One GPU R9 280X hashrate is ok. Is 20-21 MH/s. And problem i have with two GPU card R9 290X. Before i have in this card 46-47 MH/s. But now is very critical low....20-21 MH/s. I send photo screenshot and settings my miner. I test previous version and too problem....I test another software and too...Before this time all ok....

EthDcrMiner64.exe -mode 1 -esm 1 -epool eu1.ethpool.org:3333 -ewal 0x7efa35203ded3af8394854022541a2cbfa73cc05.marian2 -epsw x -estale 0

http://s32.postimg.org/6q7dtz879/r290x.jpg

Please help me friend....where is the problem?

Thanks for the info, very helpful. So in your opinion, I should use ethminer doing solo on my Geth? Even though CMD give me a higher hash rate? With either I get 103mh on 1 rig, with CMD I get 120mh. With all my hw, using Ethminer its 460mh, with CMD its 550Mh. Considerable difference.

Thanks,

I am not getting the below error when CDM starts,


ETH: Connected (10.110.150.88:8545)
ETH: Received error: {"jsonrpc":"2.0","id":0,"error":{"code":-32000,"message":"mining not ready"}}
No pool specified for Decred! Ethereum-only mining mode is enabled
ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
ETH: HTTP SOLO mode
Ethereum HTTP requests time (-etht) is set to 200 ms
Watchdog enabled

ETH: 05/19/16-21:14:20 - New job (target 0x00000000000706a0) from 10.110.150.88:8545
ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s