coin123123
|
|
June 14, 2014, 10:53:11 AM |
|
something wrong with x13 pool lately?
here my last payouts:
2014-06-13 23:04:45 0.01450667 BTC 2014-06-12 23:29:25 0.01715827 BTC 2014-06-11 23:50:53 0.00995395 BTC 2014-06-10 23:28:39 0.01482573 BTC 2014-06-09 23:59:27 0.04581396 BTC 2014-06-08 23:10:20 0.04279376 BTC 2014-06-07 23:44:04 0.05589293 BTC 2014-06-06 23:37:20 0.05910286 BTC
last days seems i get third of what i should?
|
|
|
|
Xenocyde
|
|
June 14, 2014, 11:24:22 AM |
|
Ya I got 0.006 for 3 days, then the pool got some problems with servers and rogue coins or something few days ago and profitability decreased to 0.002 - 0.003 tops. Dunno if it's a pool problem or coins took a hit because BTC is going down a bit.
|
|
|
|
Undland
Legendary
Offline
Activity: 1120
Merit: 1055
|
|
June 14, 2014, 12:44:58 PM |
|
i got 11% rejected!
|
|
|
|
schnauzr
Member
Offline
Activity: 72
Merit: 10
|
|
June 14, 2014, 03:36:09 PM |
|
Hi merc82, can you help me understand the vardiff please? how come sometimes i get cycles such as the below I'm hasing with 3 Furys, 4 Mh/s total. But the diff is so ridiculously high (16384!) that I haven't submitted a share in 5 minutes. This happens often, and it takes quite a while for the pool to recognize that the diff is too damn high: And eventually it goes back to a reasonable diff but it doesn't stay there... eventually it spikes again and hangs the share submissions for who knows how long. Its not just this way for my Furys on Scrypt but my rigs on X11 and X13. Is there a way to request a steady diff by my miner's config?
|
|
|
|
Hueristic
Legendary
Offline
Activity: 3976
Merit: 5392
Doomed to see the future and unable to prevent it
|
|
June 14, 2014, 05:09:45 PM |
|
Hi merc82, can you help me understand the vardiff please? how come sometimes i get cycles such as the below I'm hasing with 3 Furys, 4 Mh/s total. But the diff is so ridiculously high (16384!) that I haven't submitted a share in 5 minutes. This happens often, and it takes quite a while for the pool to recognize that the diff is too damn high: And eventually it goes back to a reasonable diff but it doesn't stay there... eventually it spikes again and hangs the share submissions for who knows how long. Its not just this way for my Furys on Scrypt but my rigs on X11 and X13. Is there a way to request a steady diff by my miner's config? Are those HW errors normal? Looks horrible.
|
“Bad men need nothing more to compass their ends, than that good men should look on and do nothing.”
|
|
|
schnauzr
Member
Offline
Activity: 72
Merit: 10
|
|
June 14, 2014, 06:11:15 PM Last edit: June 14, 2014, 09:25:47 PM by schnauzr |
|
Normal for zeus based ASICS. I've actually seen worse.
|
|
|
|
lsss
Newbie
Offline
Activity: 27
Merit: 0
|
|
June 14, 2014, 06:55:46 PM |
|
I've modified the X11/X13 switching ports
The previous port will now stay alive for 60 seconds before closing, this should allow sgminer to see the new port before it closes the old port, allowing the failover to happen much quicker.
Thanks!
I don't know if this has anything to do with this or not: Buy just today I notice ~4 min +/- 30 sec to make the switch. I'm not sure where I was before, but I never noticed anything this long. I tried --failover-only (where I didn't have it set before) and no difference. Could it have to do with : --expiry 1 --scan-time 1 --queue 0 For now i'm off of the algo switching ports and on 4440.
|
|
|
|
Hueristic
Legendary
Offline
Activity: 3976
Merit: 5392
Doomed to see the future and unable to prevent it
|
|
June 14, 2014, 09:36:47 PM |
|
Normal for zeus based ASICS. I've actually seen worse. Rotf
|
“Bad men need nothing more to compass their ends, than that good men should look on and do nothing.”
|
|
|
bullus
|
|
June 14, 2014, 10:08:29 PM |
|
I've modified the X11/X13 switching ports
The previous port will now stay alive for 60 seconds before closing, this should allow sgminer to see the new port before it closes the old port, allowing the failover to happen much quicker.
Thanks!
I don't know if this has anything to do with this or not: Buy just today I notice ~4 min +/- 30 sec to make the switch. I'm not sure where I was before, but I never noticed anything this long. I tried --failover-only (where I didn't have it set before) and no difference. Could it have to do with : --expiry 1 --scan-time 1 --queue 0 For now i'm off of the algo switching ports and on 4440. For me it's switching in 30 seconds..I change it to 10 sec now https://bitcointalk.org/index.php?topic=632503.msg7313568#msg7313568
|
btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
|
|
|
schnauzr
Member
Offline
Activity: 72
Merit: 10
|
|
June 14, 2014, 10:25:58 PM |
|
Normal for zeus based ASICS. I've actually seen worse. Rotf
|
|
|
|
merc82 (OP)
|
|
June 14, 2014, 11:15:58 PM |
|
Normal for zeus based ASICS. I've actually seen worse. Rotf Lol, love the images folks So I made a change to the vardiff settings, let me know if it still gets outrageous.. this was on the x11/x13 ports. Previously it was looking for a share every 15 seconds, but some of the coins we mine at low difficulty find blocks faster than this when we get on them, thus the block notification spam. I've dropped this to ~5 seconds.. hope it helps. This is an on-going tuning battle, I apologize for not having the immediate solution, but I promise to keep making changes to better profits overall as often as possible If you guys have a favorite ideal difficulty, I can open a set-difficulty port
|
Rent some Hash @ MiningRigRentals!Lease out your rig, or rent some extra hash today! Live Hashrate graphs, multiple backup pools, many algos and fast and friendly support as well
|
|
|
schnauzr
Member
Offline
Activity: 72
Merit: 10
|
|
June 14, 2014, 11:56:53 PM |
|
Haha awesome, thanks merc. Your diligence is much appreciated by all of us I'm sure. Will let you know if diff keeps going nuts moving forward.
|
|
|
|
Xenocyde
|
|
June 15, 2014, 04:59:43 AM |
|
I've modified the X11/X13 switching ports
The previous port will now stay alive for 60 seconds before closing, this should allow sgminer to see the new port before it closes the old port, allowing the failover to happen much quicker.
Thanks!
I don't know if this has anything to do with this or not: Buy just today I notice ~4 min +/- 30 sec to make the switch. I'm not sure where I was before, but I never noticed anything this long. I tried --failover-only (where I didn't have it set before) and no difference. Could it have to do with : --expiry 1 --scan-time 1 --queue 0 For now i'm off of the algo switching ports and on 4440. For me it's switching in 30 seconds..I change it to 10 sec now https://bitcointalk.org/index.php?topic=632503.msg7313568#msg7313568I'm on 4010 and 4011 ports but I still get 3-4 minutes between algo switch sometimes. How do I change it to 10 seconds?
|
|
|
|
Spacewide
Newbie
Offline
Activity: 38
Merit: 0
|
|
June 15, 2014, 08:14:57 AM |
|
something wrong with x13 pool lately?
here my last payouts:
2014-06-13 23:04:45 0.01450667 BTC 2014-06-12 23:29:25 0.01715827 BTC 2014-06-11 23:50:53 0.00995395 BTC 2014-06-10 23:28:39 0.01482573 BTC 2014-06-09 23:59:27 0.04581396 BTC 2014-06-08 23:10:20 0.04279376 BTC 2014-06-07 23:44:04 0.05589293 BTC 2014-06-06 23:37:20 0.05910286 BTC
last days seems i get third of what i should?
Same here! Did you figure out why already? I've been breaking my head about it.
|
|
|
|
coin123123
|
|
June 15, 2014, 10:08:47 AM |
|
something wrong with x13 pool lately?
here my last payouts:
2014-06-13 23:04:45 0.01450667 BTC 2014-06-12 23:29:25 0.01715827 BTC 2014-06-11 23:50:53 0.00995395 BTC 2014-06-10 23:28:39 0.01482573 BTC 2014-06-09 23:59:27 0.04581396 BTC 2014-06-08 23:10:20 0.04279376 BTC 2014-06-07 23:44:04 0.05589293 BTC 2014-06-06 23:37:20 0.05910286 BTC
last days seems i get third of what i should?
Same here! Did you figure out why already? I've been breaking my head about it. nope. rejected 3-4% and i get rejected usualy on coin change when it writes "job not found", all seems good but when looking at cgminer windows i get "pool slowdown" "pool not responding" and "waiting for work to be available from pools" very often, tried all US and EU pools same result. switched half of my miners to x11 will see how it goes
|
|
|
|
Spacewide
Newbie
Offline
Activity: 38
Merit: 0
|
|
June 15, 2014, 11:31:14 AM Last edit: June 15, 2014, 01:32:53 PM by Spacewide |
|
something wrong with x13 pool lately?
here my last payouts:
2014-06-13 23:04:45 0.01450667 BTC 2014-06-12 23:29:25 0.01715827 BTC 2014-06-11 23:50:53 0.00995395 BTC 2014-06-10 23:28:39 0.01482573 BTC 2014-06-09 23:59:27 0.04581396 BTC 2014-06-08 23:10:20 0.04279376 BTC 2014-06-07 23:44:04 0.05589293 BTC 2014-06-06 23:37:20 0.05910286 BTC
last days seems i get third of what i should?
Same here! Did you figure out why already? I've been breaking my head about it. nope. rejected 3-4% and i get rejected usualy on coin change when it writes "job not found", all seems good but when looking at cgminer windows i get "pool slowdown" "pool not responding" and "waiting for work to be available from pools" very often, tried all US and EU pools same result. switched half of my miners to x11 will see how it goes I'll try to figure this out later today. Port 4440 right? Opening a ticket in the meantime
|
|
|
|
Xenocyde
|
|
June 15, 2014, 03:25:18 PM |
|
I've modified the X11/X13 switching ports
The previous port will now stay alive for 60 seconds before closing, this should allow sgminer to see the new port before it closes the old port, allowing the failover to happen much quicker.
Thanks!
I don't know if this has anything to do with this or not: Buy just today I notice ~4 min +/- 30 sec to make the switch. I'm not sure where I was before, but I never noticed anything this long. I tried --failover-only (where I didn't have it set before) and no difference. Could it have to do with : --expiry 1 --scan-time 1 --queue 0 For now i'm off of the algo switching ports and on 4440. For me it's switching in 30 seconds..I change it to 10 sec now https://bitcointalk.org/index.php?topic=632503.msg7313568#msg7313568I'm on 4010 and 4011 ports but I still get 3-4 minutes between algo switch sometimes. How do I change it to 10 seconds? Any solution here guys? I moved my mining rig between houses, thus I have new internet provider now (slower one) and it now takes more than 10 mins to switch algos sometimes.
|
|
|
|
bullus
|
|
June 15, 2014, 08:17:55 PM |
|
I've modified the X11/X13 switching ports
The previous port will now stay alive for 60 seconds before closing, this should allow sgminer to see the new port before it closes the old port, allowing the failover to happen much quicker.
Thanks!
I don't know if this has anything to do with this or not: Buy just today I notice ~4 min +/- 30 sec to make the switch. I'm not sure where I was before, but I never noticed anything this long. I tried --failover-only (where I didn't have it set before) and no difference. Could it have to do with : --expiry 1 --scan-time 1 --queue 0 For now i'm off of the algo switching ports and on 4440. For me it's switching in 30 seconds..I change it to 10 sec now https://bitcointalk.org/index.php?topic=632503.msg7313568#msg7313568I'm on 4010 and 4011 ports but I still get 3-4 minutes between algo switch sometimes. How do I change it to 10 seconds? "failover-switch-delay" : "10", "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", "no-pool-disable" : true } sgminer 4.2.1 - Started: [2014-06-15 21:55:03] - [0 days 00:24:42] -------------------------------------------------------------------------------- (5s):2.326M (avg):2.294Mh/s | A:0 R:0 HW:0 WU:0.027/m ST: 1 SS: 0 NB: 113 LW: 74 GF: 0 RF: 0 Connected to am02 x11 multi (stratum) diff 0.005 as user xxx Block: 2fde6bc5... Diff:495 Started: [22:19:41] Best share: 0.032 -------------------------------------------------------------------------------- [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit GPU 1: 42.0C 65% | 2.270M/2.397Mh/s | R: 0.0% HW:0 WU:0.032/m I:18 -------------------------------------------------------------------------------- [22:13:28] Accepted 3253888f Diff 0.020/0.005 GPU 1 at am02 x13 multi [22:14:01] am02 x13 multi stale share detected, submitting (user) [22:14:01] Accepted 83781253 Diff 0.008/0.005 GPU 1 at am02 x13 multi [22:14:17] Stratum connection to am02 x13 multi interrupted [22:14:18] am02 x13 multi not responding! [22:14:18] Switching to am02 x11 [22:14:18] am02 x11 difficulty changed to 0.005 [22:14:27] Initialising kernel darkcoin-mod.cl with bitalign, unpatched BFI, nfactor 10, n 1024 [22:14:27] Initialising kernel darkcoin-mod.cl with bitalign, unpatched BFI, nfactor 10, n 1024 [22:14:32] Accepted 90749c06 Diff 0.007/0.005 GPU 1 at am02 x11 [22:14:36] Accepted b85d9c6c Diff 0.005/0.005 GPU 1 at am02 x11 [22:15:08] Accepted 8f1227c6 Diff 0.007/0.005 GPU 1 at am02 x11 [22:15:17] Accepted 8196e8b3 Diff 0.008/0.005 GPU 1 at am02 x11 [22:15:21] am02 x13 multi alive, testing stability [22:15:31] am02 x11 stale share detected, submitting (user) [22:15:31] Accepted 45025975 Diff 0.014/0.005 GPU 1 at am02 x11 [22:15:41] Accepted 6d248e3e Diff 0.009/0.005 GPU 1 at am02 x11 [22:15:46] am02 x13 multi stable for 10 seconds [22:15:46] Switching to am02 x13 multi [22:15:46] Initialising kernel marucoin-modold.cl with bitalign, unpatched BFI, nfactor 10, n 1024 [22:15:46] Initialising kernel marucoin-modold.cl with bitalign, unpatched BFI, nfactor 10, n 1024 [22:16:37] Accepted 8d179e4d Diff 0.007/0.005 GPU 1 at am02 x13 multi [22:17:37] Accepted 53227a0d Diff 0.012/0.005 GPU 1 at am02 x13 multi [22:17:38] Accepted 36886cab Diff 0.018/0.005 GPU 1 at am02 x13 multi [22:17:59] Accepted 9897dd89 Diff 0.007/0.005 GPU 1 at am02 x13 multi [22:18:02] Accepted afd0347a Diff 0.006/0.005 GPU 1 at am02 x13 multi [22:18:03] Accepted 6c0eaf98 Diff 0.009/0.005 GPU 1 at am02 x13 multi [22:18:38] am02 x11 multi alive, testing stability [b][22:18:46] am02 x11 multi stable for 10 seconds[/b] [22:18:46] Switching to am02 x11 multi [22:18:46] Accepted a758c963 Diff 0.006/0.005 GPU 1 at am02 x13 multi [22:18:47] Initialising kernel darkcoin-mod.cl with bitalign, unpatched BFI, nfactor 10, n 1024 [22:18:47] Initialising kernel darkcoin-mod.cl with bitalign, unpatched BFI, nfactor 10, n 1024 [22:19:08] Accepted b21c8211 Diff 0.006/0.005 GPU 1 at am02 x11 multi [22:19:09] Accepted b4cea21f Diff 0.006/0.005 GPU 1 at am02 x11 multi [22:19:23] Accepted 6d58391f Diff 0.009/0.005 GPU 1 at am02 x11 multi [22:19:26] Accepted 370ab0f5 Diff 0.018/0.005 GPU 1 at am02 x11 multi [22:19:41] Accepted 20b32269 Diff 0.031/0.005 GPU 1 at am02 x11 multi [22:19:43] Accepted 1f6729ff Diff 0.032/0.005 GPU 1 at am02 x11 multi
|
btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
|
|
|
Xenocyde
|
|
June 15, 2014, 08:41:47 PM |
|
I modified all settings to be mostly like yours and miner is not getting any work from pool. I'll just modify the failover-switch-delay to 10 only.
L.E.: I got work but miner first waited 5-6 minutes and said my ports are wrong. I'll keep settings like yours and see if all goes well, if not I'll just modify the failover.
|
|
|
|
bullus
|
|
June 15, 2014, 11:17:21 PM |
|
I modified all settings to be mostly like yours and miner is not getting any work from pool. I'll just modify the failover-switch-delay to 10 only.
L.E.: I got work but miner first waited 5-6 minutes and said my ports are wrong. I'll keep settings like yours and see if all goes well, if not I'll just modify the failover.
How does ur pool config look like? Which cards are u using? Drivers?
|
btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
|
|
|
|