Topic: [ANN][MULTI][VARDIFF] TradeMyBit MULTIALGO Profit Swap w/ Optional Auto-exchange - page 22. (Read 153090 times)
June 20, 2014, 12:16:08 AM
Ok. Now it stores wallet's address by didn't make payout...
June 19, 2014, 07:05:28 AM
Seems like stratum+tcp://am01.eu.trademybit.com not working today.
June 19, 2014, 05:50:15 AM
Worker monitoring still isn't working. Lost a couple of days of mining because of that recently. I have submitted an issue on your support portal, Merc82. Could you please look into this?
/Jakob
/Jakob
June 19, 2014, 01:03:46 AM
Just woke up and this time miner idled for 7 hours 
Might be because I switched to the build Bullus posted a few days ago... I'll try the latest build, see if it still idles after X hours.
Might be because I switched to the build Bullus posted a few days ago... I'll try the latest build, see if it still idles after X hours. June 18, 2014, 11:59:55 PM
I can't make a withdrawal of DIGIT. Pool says "DIGIT - Invalid Payout Address!". But i just did copy-paste my address from wallet... What should i do?
June 18, 2014, 01:07:34 PM
Nvidia miners rejoice! I found a simple way to take advantage of the new ccminer v1.2 with X11 and X13 support and TMB's new algo profit switching feature! 
I've been running this batch for about a day now with good results. The timing variables at the end may not be optimum, but seem to be working thus far. Any improvements to this technique are welcome of course.
Here's the simple technique I'm using in a windows batch file:
The idea here, is that only one of the above ports is open at a time, so when a port closes because it's no longer the most profitable algo, ccminer will exit and another ccminer with the other algo and port will start. The loop ensures that it keeps trying until it finds an open port regardless of which algo we're switching to.
I have noticed that when TMB switches (even if it's the same algo but a different coin) that the loop may repeat once or twice, but it always ends up mining the correct coin as soon as the port opens up. It's a little weird to watch, but it all happens pretty fast.
This is of course for Windows. I'm sure the same technique could be used in a script for Linux and I'm hoping some Linux guru will post an example here soon.
I've been running this batch for about a day now with good results. The timing variables at the end may not be optimum, but seem to be working thus far. Any improvements to this technique are welcome of course.
Here's the simple technique I'm using in a windows batch file:
Code:
cd C:\Users\Public\Coin\Miners\ccminer-v1.2\x86\
:loop
ccminer.exe -a x11 -o stratum+tcp://west01.us.trademybit.com:4010 -u WebID.worker -p password -r 2 -R 3 -T 5
ccminer.exe -a x13 -o stratum+tcp://west01.us.trademybit.com:4011 -u WebID.worker -p password -r 2 -R 3 -T 5
goto loop
The idea here, is that only one of the above ports is open at a time, so when a port closes because it's no longer the most profitable algo, ccminer will exit and another ccminer with the other algo and port will start. The loop ensures that it keeps trying until it finds an open port regardless of which algo we're switching to.
I have noticed that when TMB switches (even if it's the same algo but a different coin) that the loop may repeat once or twice, but it always ends up mining the correct coin as soon as the port opens up. It's a little weird to watch, but it all happens pretty fast.
This is of course for Windows. I'm sure the same technique could be used in a script for Linux and I'm hoping some Linux guru will post an example here soon.
June 18, 2014, 11:14:17 AM
.
June 18, 2014, 01:21:03 AM
Just woke up and checked my miner, looks like it stopped receiving work 1H 50 minutes ago and idled til now. Anything happened at that moment to the X11 or X13 pools? Was mining on the X11 and it didn't switch to X13, it just stopped receivinng work and idled.
June 17, 2014, 03:49:08 PM
Just thought I should contribute to this thread here.
Here is my config for Trademybit multi algo x11/x13
I was getting 2-3 min delays between algo switches but the problem was resolved by making the port that closes the FIRST pool in the list, and leaving the port that is ALWAYS OPEN as the second one.
The logic here (this will probably be addressed in later releases but for the time being its smooth): First pool opens and closes. If x11 is more profitable, x13 shuts, insta fail-over to x11, when x13 is more profitable, pool port opens up, since its first pool, it will go back to it from x11.
For what ever reason the miner didn't like the fact that both could be closed or overlap... no idea why... but it works now.
This is using Catalyst 14.4
sgminer.conf =
This is for my 290 @ stock clocks using this build:
https://mega.co.nz/#!Ld5QASiI!cS1ETIXI_-jdvx6ZW93rD-IYY91zcWG4B24ZbYs2Ik8
x11 = 4Mhs
x13 = 3Mhs
http://pastebin.com/eNbaahbY
Heres one for my 5x 280x Rig using the same build in the megalink:
x11 = 3.1-3.2
x13 = 2.2-2.4 (Cards are beat to shit from scrypt mining their hashes swing up and down)
http://pastebin.com/FpvMKVBc
Credit goes to Pelk for the pool list configuration at #pool from Trademybit IRC.
Hope this will help.
Here is my config for Trademybit multi algo x11/x13
I was getting 2-3 min delays between algo switches but the problem was resolved by making the port that closes the FIRST pool in the list, and leaving the port that is ALWAYS OPEN as the second one.
The logic here (this will probably be addressed in later releases but for the time being its smooth): First pool opens and closes. If x11 is more profitable, x13 shuts, insta fail-over to x11, when x13 is more profitable, pool port opens up, since its first pool, it will go back to it from x11.
For what ever reason the miner didn't like the fact that both could be closed or overlap... no idea why... but it works now.
This is using Catalyst 14.4
sgminer.conf =
This is for my 290 @ stock clocks using this build:
https://mega.co.nz/#!Ld5QASiI!cS1ETIXI_-jdvx6ZW93rD-IYY91zcWG4B24ZbYs2Ik8
x11 = 4Mhs
x13 = 3Mhs
http://pastebin.com/eNbaahbY
Heres one for my 5x 280x Rig using the same build in the megalink:
x11 = 3.1-3.2
x13 = 2.2-2.4 (Cards are beat to shit from scrypt mining their hashes swing up and down)
http://pastebin.com/FpvMKVBc
Credit goes to Pelk for the pool list configuration at #pool from Trademybit IRC.
Hope this will help.
June 17, 2014, 01:32:24 PM
Can you give an example of your Multi-Algo SGMiner v5 pool config file?
see here
https://bitcointalksearch.org/topic/m.7331899
yes it can, u could the search the other topic..I don't use it because of the higher wattage and with tmb there isn't a setting for yet. (No Scrypt and scrypt-n multi algo port)
June 17, 2014, 01:28:41 PM
Can you give an example of your Multi-Algo SGMiner v5 pool config file?
see here
https://bitcointalksearch.org/topic/m.7331899
June 17, 2014, 01:22:23 PM
Do notifications for idle workers work for anyone? Or is it just broken for me?
June 17, 2014, 11:06:07 AM
Can you give an example of your Multi-Algo SGMiner v5 pool config file?
see here
https://bitcointalksearch.org/topic/m.7331899
June 17, 2014, 08:05:06 AM
Can you give an example of your Multi-Algo SGMiner v5 pool config file?
June 16, 2014, 05:35:01 PM
I'm using sgminer_v5 for multi-algo switching
see dl https://bitcointalksearch.org/topic/m.7226879
I also don't see any rare settings, did u try lookup-gap 0? or put the shaders in it?
my config
see dl https://bitcointalksearch.org/topic/m.7226879
I also don't see any rare settings, did u try lookup-gap 0? or put the shaders in it?
my config
Code:
"extranonce-subscribe" : true,
"remove-disabled" : true,
"api-allow" : "W:127.0.0.1",
"api-listen" : true,
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "10",
"failover-only" : true,
"kernel-path" : "D:\\sgminer_v5_0_10062014",
"log" : "5",
"queue" : "1",
"scan-time" : "7",
"shares" : "0",
"failover-switch-delay" : "10",
"gpu-threads" : "2",
"gpu-dyninterval" : "7",
"gpu-engine" : "0",
"gpu-fan" : "65",
"gpu-platform" : "0",
"gpu-memclock" : "0",
"gpu-memdiff" : "0",
"gpu-powertune" : "8",
"gpu-vddc" : "0",
"intensity" : "18",
"temp-target" : "75",
"temp-overheat" : "85",
"temp-cutoff" : "95",
"temp-hysteresis" : "3",
"vectors" : "1",
"worksize" : "256",
"lookup-gap" : "0",
"shaders" : "1792",
"thread-concurrency" : "8192",
"device" : "0,2,3,4",
"hamsi-expand-big" : "4",
"no-pool-disable" : true
}
June 16, 2014, 05:30:02 PM
Hello lads
I'm mostly running x11 and x13 as many of you probably.
Although I'm having a many stale shares.
As you can see above, for now 36 stales.
This is happening since 10th of June.
Same stratum, same network at work, same hardware and same config.
Any ideas guys?
queue 1, scantime 7, expiry 10
Thank you
I'm mostly running x11 and x13 as many of you probably.
Although I'm having a many stale shares.
Code:
sgminer 4.1.0 - Started: [2014-06-16 17:01:49] - [0 days 05:41:45]
-------------------------------------------------------------------------------
(5s):16.99M (avg):16.71Mh/s | A:2690 R:81 HW:0 WU:0.235/m
ST: 1 SS: 36 NB: 872 LW: 50521 GF: 1 RF: 0
Connected to am01.eu.trademybit.com:4440 (stratum) diff 0.028 as user
Block: 350a6e2e... Diff:1.06K Started: [22:43:15] Best share: 76
-------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 55.0C 2332RPM | 3.357M/3.349Mh/s | A:562 R: 2.8% HW:0 WU:0.047/m I:18
GPU 1: 59.0C 2142RPM | 3.368M/3.349Mh/s | A:549 R: 3.7% HW:0 WU:0.046/m I:18
GPU 2: 55.0C 2309RPM | 3.362M/3.348Mh/s | A:535 R: 2.8% HW:0 WU:0.047/m I:17
GPU 3: 58.0C 2155RPM | 3.343M/3.331Mh/s | A:507 R: 2.8% HW:0 WU:0.048/m I:18
GPU 4: 51.0C 2242RPM | 3.318M/3.330Mh/s | A:537 R: 3.6% HW:0 WU:0.047/m I:18
8
[22:42:42] Accepted 07b14268 Diff 0.130/0.028 GPU 1 at Pool 0
[22:42:54] Accepted 074604d7 Diff 0.137/0.028 GPU 1 at Pool 0
[22:42:56] Accepted 1569f97f Diff 0.047/0.028 GPU 2 at Pool 0
[22:43:01] Accepted 0b96e6f1 Diff 0.086/0.028 GPU 3 at Pool 0
[22:43:14] Accepted 1c463535 Diff 0.035/0.028 GPU 1 at Pool 0
[22:43:15] Network diff set to 1.06K
[22:43:15] Stratum from Pool 0 detected new block
[22:43:16] Accepted 03b09563 Diff 0.271/0.028 GPU 3 at Pool 0
[22:43:18] Accepted 04f9806a Diff 0.201/0.028 GPU 0 at Pool 0
As you can see above, for now 36 stales.
This is happening since 10th of June.
Same stratum, same network at work, same hardware and same config.
Any ideas guys?
queue 1, scantime 7, expiry 10
Thank you
I'm using the same and don't have stales but using the am02 stratum
What config do u use?
Hello
I see you run a higher version of SGminer + x11/x13mod. Can you post (pm) a downloadlink or place a link to the forumthread?
My config (batfile) goes as following.
Code:
del *.bin
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
sgminer_x11x13mod_03_06_2014\sgminer.exe -k x11mod -o stratum+tcp://am01.eu.trademybit.com:4440 -u xxx -p xxx -I 18 -w 256 --thread-concurrency 8192 --lookup-gap 2 -g 2 --gpu-engine 1150 --gpu-memclock 1500 --auto-fan --gpu-fan 55-85 --temp-cutoff 80 --temp-overheat 76 --temp-target 73 --no-submit-stale
I can't see any issues in that configuration though.
Best regards,
-sw
June 16, 2014, 04:46:35 PM
Hello lads
I'm mostly running x11 and x13 as many of you probably.
Although I'm having a many stale shares.
As you can see above, for now 36 stales.
This is happening since 10th of June.
Same stratum, same network at work, same hardware and same config.
Any ideas guys?
queue 1, scantime 7, expiry 10
Thank you
I'm mostly running x11 and x13 as many of you probably.
Although I'm having a many stale shares.
Code:
sgminer 4.1.0 - Started: [2014-06-16 17:01:49] - [0 days 05:41:45]
-------------------------------------------------------------------------------
(5s):16.99M (avg):16.71Mh/s | A:2690 R:81 HW:0 WU:0.235/m
ST: 1 SS: 36 NB: 872 LW: 50521 GF: 1 RF: 0
Connected to am01.eu.trademybit.com:4440 (stratum) diff 0.028 as user
Block: 350a6e2e... Diff:1.06K Started: [22:43:15] Best share: 76
-------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 55.0C 2332RPM | 3.357M/3.349Mh/s | A:562 R: 2.8% HW:0 WU:0.047/m I:18
GPU 1: 59.0C 2142RPM | 3.368M/3.349Mh/s | A:549 R: 3.7% HW:0 WU:0.046/m I:18
GPU 2: 55.0C 2309RPM | 3.362M/3.348Mh/s | A:535 R: 2.8% HW:0 WU:0.047/m I:17
GPU 3: 58.0C 2155RPM | 3.343M/3.331Mh/s | A:507 R: 2.8% HW:0 WU:0.048/m I:18
GPU 4: 51.0C 2242RPM | 3.318M/3.330Mh/s | A:537 R: 3.6% HW:0 WU:0.047/m I:18
8
[22:42:42] Accepted 07b14268 Diff 0.130/0.028 GPU 1 at Pool 0
[22:42:54] Accepted 074604d7 Diff 0.137/0.028 GPU 1 at Pool 0
[22:42:56] Accepted 1569f97f Diff 0.047/0.028 GPU 2 at Pool 0
[22:43:01] Accepted 0b96e6f1 Diff 0.086/0.028 GPU 3 at Pool 0
[22:43:14] Accepted 1c463535 Diff 0.035/0.028 GPU 1 at Pool 0
[22:43:15] Network diff set to 1.06K
[22:43:15] Stratum from Pool 0 detected new block
[22:43:16] Accepted 03b09563 Diff 0.271/0.028 GPU 3 at Pool 0
[22:43:18] Accepted 04f9806a Diff 0.201/0.028 GPU 0 at Pool 0
As you can see above, for now 36 stales.
This is happening since 10th of June.
Same stratum, same network at work, same hardware and same config.
Any ideas guys?
queue 1, scantime 7, expiry 10
Thank you
I'm using the same and don't have stales but using the am02 stratum
Code:
sgminer 4.2.1 - Started: [2014-06-16 12:07:53] - [0 days 11:37:52]
--------------------------------------------------------------------------------
(5s):11.18M (avg):11.35Mh/s | A:2 R:0 HW:0 WU:0.152/m
ST: 1 SS: 0 NB: 2202 LW: 1733 GF: 1 RF: 0
Connected to am01 x11 multi (stratum) diff 0.032 as user xxxx
Block: 79a2f206... Diff:311 Started: [23:45:44] Best share: 0.440
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 57.0C 2702RPM | 2.854M/2.842Mh/s | R: 0.0% HW:0 WU:0.039/m I:18
GPU 2: 54.0C 3160RPM | 2.843M/2.834Mh/s | R: 0.0% HW:0 WU:0.038/m I:18
GPU 3: 51.0C 3172RPM | 2.813M/2.822Mh/s | R: 3.8% HW:0 WU:0.035/m I:18
GPU 4: 51.0C 2777RPM | 2.846M/2.860Mh/s | R: 5.3% HW:0 WU:0.039/m I:18
--------------------------------------------------------------------------------
[23:41:26] Rejected 13771b70 Diff 0.051/0.021 GPU 3 am01 x11 multi (job not found)
[23:41:36] Accepted 0f009e13 Diff 0.067/0.021 GPU 4 at am01 x11 multi
[23:41:37] Accepted 1ccb7a65 Diff 0.035/0.021 GPU 2 at am01 x11 multi
[23:41:37] Accepted 02600516 Diff 0.421/0.021 GPU 4 at am01 x11 multi
[23:41:49] Accepted 1a5b951c Diff 0.038/0.021 GPU 2 at am01 x11 multi
[23:41:50] Accepted 2c2a9e37 Diff 0.023/0.021 GPU 2 at am01 x11 multi
[23:41:53] Accepted 1d99c87a Diff 0.034/0.021 GPU 4 at am01 x11 multi
[23:41:53] Accepted 04179b78 Diff 0.244/0.021 GPU 0 at am01 x11 multi
[23:42:01] Accepted 0f1ac7da Diff 0.066/0.021 GPU 4 at am01 x11 multi
[23:42:24] Accepted 288e0ee9 Diff 0.025/0.021 GPU 2 at am01 x11 multi
[23:42:28] Accepted 06bb981a Diff 0.149/0.021 GPU 3 at am01 x11 multi
[23:42:36] Accepted 1d883597 Diff 0.034/0.021 GPU 2 at am01 x11 multi
[23:42:37] Accepted 1598df07 Diff 0.046/0.021 GPU 4 at am01 x11 multi
[23:42:38] Accepted 22cacb79 Diff 0.029/0.021 GPU 4 at am01 x11 multi
[23:42:38] Accepted 05ef7f75 Diff 0.168/0.021 GPU 3 at am01 x11 multi
[23:42:43] Accepted 1376cfb7 Diff 0.051/0.021 GPU 0 at am01 x11 multi
[23:42:46] Accepted 2b3fa527 Diff 0.023/0.021 GPU 2 at am01 x11 multi
[23:42:55] Accepted 2c483dd3 Diff 0.023/0.021 GPU 0 at am01 x11 multi
[23:42:57] Accepted 0f33318f Diff 0.066/0.021 GPU 3 at am01 x11 multi
[23:43:01] Accepted 253dee8e Diff 0.027/0.021 GPU 2 at am01 x11 multi
[23:43:10] Accepted 039d6239 Diff 0.277/0.021 GPU 0 at am01 x11 multi
[23:43:11] Accepted 2544a4c6 Diff 0.027/0.021 GPU 0 at am01 x11 multi
[23:43:21] Accepted 1e39fed2 Diff 0.033/0.021 GPU 4 at am01 x11 multi
[23:43:30] Accepted 06f763c0 Diff 0.144/0.021 GPU 3 at am01 x11 multi
[23:43:33] Accepted 133c41e1 Diff 0.052/0.021 GPU 4 at am01 x11 multi
[23:43:46] Accepted 05e04b6b Diff 0.170/0.021 GPU 4 at am01 x11 multi
[23:43:51] Accepted 22933703 Diff 0.029/0.021 GPU 4 at am01 x11 multi
[23:43:53] Accepted 13a520ad Diff 0.051/0.021 GPU 0 at am01 x11 multi
[23:43:54] Accepted 206d7908 Diff 0.031/0.021 GPU 0 at am01 x11 multi
[23:44:07] Accepted 0ba268d1 Diff 0.086/0.021 GPU 2 at am01 x11 multi
[23:44:07] Accepted 0cac2337 Diff 0.079/0.021 GPU 4 at am01 x11 multi
[23:44:10] am01 x11 multi difficulty changed to 0.032
[23:44:54] Accepted 0e5522f9 Diff 0.070/0.032 GPU 0 at am01 x11 multi
[23:45:17] Accepted 048a8f08 Diff 0.220/0.032 GPU 3 at am01 x11 multi
[23:45:23] Accepted 059e08f5 Diff 0.178/0.032 GPU 2 at am01 x11 multi
[23:45:23] Accepted 13d8fc44 Diff 0.050/0.032 GPU 0 at am01 x11 multi
What config do u use?
Try to deleted the global "algorithim" and change the kernelpath like I did, to your directory offcourse.
U can try 14.4.
U can try 14.4.
I deleted global algo entry and added correct kernel path but miner warned me there's a JSON error - can't find valid pool so I deleted the kernel path entry and all works OK now, no 6 mins delay upon miner restart anymore. Also installed catalyst 14.4 but don't see any hashrate improvements yet and need to leave miner run longer to determine stability. Thanks for tips, I appreciate the help
Tips? Thanks
|
|
\/
June 16, 2014, 03:45:10 PM
Hello lads
I'm mostly running x11 and x13 as many of you probably.
Although I'm having a many stale shares.
As you can see above, for now 36 stales.
This is happening since 10th of June.
Same stratum, same network at work, same hardware and same config.
Any ideas guys?
queue 1, scantime 7, expiry 10
Thank you
I'm mostly running x11 and x13 as many of you probably.
Although I'm having a many stale shares.
Code:
sgminer 4.1.0 - Started: [2014-06-16 17:01:49] - [0 days 05:41:45]
-------------------------------------------------------------------------------
(5s):16.99M (avg):16.71Mh/s | A:2690 R:81 HW:0 WU:0.235/m
ST: 1 SS: 36 NB: 872 LW: 50521 GF: 1 RF: 0
Connected to am01.eu.trademybit.com:4440 (stratum) diff 0.028 as user
Block: 350a6e2e... Diff:1.06K Started: [22:43:15] Best share: 76
-------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 55.0C 2332RPM | 3.357M/3.349Mh/s | A:562 R: 2.8% HW:0 WU:0.047/m I:18
GPU 1: 59.0C 2142RPM | 3.368M/3.349Mh/s | A:549 R: 3.7% HW:0 WU:0.046/m I:18
GPU 2: 55.0C 2309RPM | 3.362M/3.348Mh/s | A:535 R: 2.8% HW:0 WU:0.047/m I:17
GPU 3: 58.0C 2155RPM | 3.343M/3.331Mh/s | A:507 R: 2.8% HW:0 WU:0.048/m I:18
GPU 4: 51.0C 2242RPM | 3.318M/3.330Mh/s | A:537 R: 3.6% HW:0 WU:0.047/m I:18
8
[22:42:42] Accepted 07b14268 Diff 0.130/0.028 GPU 1 at Pool 0
[22:42:54] Accepted 074604d7 Diff 0.137/0.028 GPU 1 at Pool 0
[22:42:56] Accepted 1569f97f Diff 0.047/0.028 GPU 2 at Pool 0
[22:43:01] Accepted 0b96e6f1 Diff 0.086/0.028 GPU 3 at Pool 0
[22:43:14] Accepted 1c463535 Diff 0.035/0.028 GPU 1 at Pool 0
[22:43:15] Network diff set to 1.06K
[22:43:15] Stratum from Pool 0 detected new block
[22:43:16] Accepted 03b09563 Diff 0.271/0.028 GPU 3 at Pool 0
[22:43:18] Accepted 04f9806a Diff 0.201/0.028 GPU 0 at Pool 0
As you can see above, for now 36 stales.
This is happening since 10th of June.
Same stratum, same network at work, same hardware and same config.
Any ideas guys?
queue 1, scantime 7, expiry 10
Thank you
June 16, 2014, 07:11:13 AM
Try to deleted the global "algorithim" and change the kernelpath like I did, to your directory offcourse.
U can try 14.4.
U can try 14.4.
I deleted global algo entry and added correct kernel path but miner warned me there's a JSON error - can't find valid pool so I deleted the kernel path entry and all works OK now, no 6 mins delay upon miner restart anymore. Also installed catalyst 14.4 but don't see any hashrate improvements yet and need to leave miner run longer to determine stability. Thanks for tips, I appreciate the help
June 16, 2014, 06:12:28 AM
i think there's something wonky with the X13 pool.
it doesn't stay alive long enough to get any work done on it.
x13 has been more profitable for the last hour or two and i've not been able to connec tto it for longer than a second or two.
it doesn't stay alive long enough to get any work done on it.
x13 has been more profitable for the last hour or two and i've not been able to connec tto it for longer than a second or two.
no problem here, just switching fine and hash x13 long enough.
Jump to: