Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 361. (Read 6590565 times)

Great news clay

@Premiermine

For me it will be easy to test how profitable is mining on your pool because I am here from start.

Block reward of 1560 XVG multiplied with percent of my shares (currently it is about 1.5-1.6%) should be approximately 23-24 XVG.  Even if I get this sum for 48h of dual mining it will be great result - 12 XVG per 24h with 3000 Mh/s which is close with WTM calculations (12.2 per day) On other pools I got between 7-10 XVG for 24h with same parameters. So pools fees of 0.4-0.5% for XVG are not the only profit for most of their owners. I hope your minig pool will prove this and in that case I am ready to pay more than 1% for mining pool fee!

For some normal work in future, you will need at least 1-2 Th/s pool hash-rate power because many people are not ready to wait 24h or more hours to see any result of their mining. I saw many of them comes, spent few hours and leave pool because don't understand how it works or just didn't have patience. 

I think you should open new topic for pool relative posts.

To be totally honest, I have not done any optimization so that the mining consumes less energy. Maybe the new version of claymore has more merit than me in reducing consumption. However, it is an unexpected gift

What percentage does 100-150w over total energy consumption?

We are going up the number of connected miners, we are slowly getting bigger hashrate, which reduces the time to receive the first block. I hope that more people continue joining. I have posted messages in different places so that more people can join, if you could collaborate posting in places that you know would be a great help.

Thanks!

Hey guys looking for some help here.

I recently setup another mining rig with 2 GPUS. I am mining to mining pool hub using only the claymore dual Algo. My system keeps shutting down, and im getting the following error in the log file. Any help would be greatly appreciated. Cards are 2 R9 290x Tri-x

11:37:48:464   314   ETH: GPU0 27.416 Mh/s, GPU1 26.402 Mh/s
11:37:48:464   314    SC - Total Speed: 807.272 Mh/s, Total Shares: 3, Rejected: 0
11:37:48:479   314    SC: GPU0 411.240 Mh/s, GPU1 396.032 Mh/s
11:37:50:823   1268   SC: put share nonce 385e3fc enonce 29b600f1
11:37:50:839   1268   SC round found 1 shares
11:37:50:854   1db8    SC: 03/01/18-11:37:50 - SHARE FOUND - (GPU 0)
11:37:50:870   1db8   send: {"id": 10, "method": "mining.submit", "params": ["Vekxst.1:x","3519","0x00000000000000013b5ec27314799fee770c445999bba161253732a5113d49a5fce38503f100b 6298256985a000000002de9c88a1314ee7426c3907f48e5e6ecc9a05b8e09b28a89c40c8face618 b0ce"]}

11:37:50:979   1db8   got 37 bytes
11:37:50:979   1db8   buf: {"id":10,"result":true,"error":null}

11:37:50:995   1db8   parse packet: 36
11:37:51:011   1db8    SC: Share accepted (140 ms)!

11:37:51:026   1db8   new buf size: 0
11:38:02:824   1ff4   GPU0 t=67C fan=56%, GPU1 t=59C fan=78%
11:38:06:059   314   send: {"id":6,"worker":"Vekxst.1:x","jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x3332798", "0x000000000000000000000000000000000000000000000000000000006766b17f"]}

11:38:06:122   314   got 36 bytes
11:38:06:122   314   buf: {"id":6,"result":true,"error":null}

11:38:06:137   314   parse packet: 35
11:38:06:137   314   new buf size: 0
11:38:11:810   2240   SC: put share nonce 2a8080f enonce adcf01e6
11:38:11:825   2240   SC round found 1 shares
11:38:11:841   1db8    SC: 03/01/18-11:38:11 - SHARE FOUND - (GPU 1)
11:38:11:841   1db8   send: {"id": 11, "method": "mining.submit", "params": ["Vekxst.1:x","3519","0x00000000000000013b5ec27314799fee770c445999bba161253732a5113d49a50f08a802e601c fad8256985a000000002de9c88a1314ee7426c3907f48e5e6ecc9a05b8e09b28a89c40c8face618 b0ce"]}

11:38:11:966   1db8   got 37 bytes
11:38:11:966   1db8   buf: {"id":11,"result":true,"error":null}

11:38:11:982   1db8   parse packet: 36
11:38:11:997   1db8    SC: Share accepted (141 ms)!

11:38:12:013   1db8   new buf size: 0
11:38:16:185   1c78   em hbt: 15, dm hbt: 15, fm hbt: 31,
11:38:16:185   1c78   watchdog - thread 0 (gpu0), hb time 31
11:38:16:185   1c78   watchdog - thread 1 (gpu0), hb time 140
11:38:16:185   1c78   watchdog - thread 2 (gpu1), hb time 15
11:38:16:201   1c78   watchdog - thread 3 (gpu1), hb time 156

has this been solved yet i have the same issue

@eqpr With those numbers, and assuming a cost of 12 cents USD per KW, you are spending 4 cents to make 7 cents (only a 3 cent profit) and that doesn´t account for the additional .5% you are loosing in ethereum due to the higher fee for dual mining (which would be about one cent more in cost). It´s up to you to decide whether spending 5 cents to make 7 cents is worth it or not (to me it def isn´t, but that is my personal opinion). Now, these numbers change constantly, so that it isn´t worth it today, doesn´t mean it might not be worth doing tomorrow or the day after that; as a miner you gotta keep on top of these calculations and see shifts that would benefit you and make the best with whatever equipment you have available.

ok hope to see live, and hope that % is greater like 2 or 3% 

less stales by about 1%

are you sure for that?

plus in your pool I'm using around 100-150w less on total power drawn

Within 1-2 days I will release new version that produces a bit less stale shares (by about 1%, at least on AMD cards), it must help to raise effective hashrate a bit.

Stop quoting the entire OP.  You hog up an entire page with that.

WTH is it with people posting the entire README!!!.txt file (and then quoting it?) lately? 

I have amd cards one of the rig with red devil does work fine when i remote desktop and I never use iGPU, it is disabled and in addition to that I also not use a dummy plug and the rig still works when I use team viewer. On another rigs though, cards - nitro+ and third rig with asus dual.. They got problems when I rdp.. As I mentioned GPU0s show 0.00..

I don't see much difference when I change -ethi. Is that redundant with the following?
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

use your motherboard as internal graphics and do not connect your gpu to your monitor

Yes I did.  Other zips I download work fine, it is just the newer dual miner that I have this issue.

Only Ether mode...my RX 580s it's just a slight bump of .200mh more that's it...but the RX 560 dropped by 1mh.. it's still the beta mining drivers and same gpu settings with custom bios as before.

Not really, but... Are you dual mining? I have found that my RX 550 4GB cards get 9.5 MH/s, but when I dual mine and tweak the dcri setting just right I get 11.5 MH/s + the additional income from dual mining. I don't see the same speed bump on my 570 or 580 cards.