|
byt411
|
 |
May 23, 2014, 07:20:05 AM |
|
CA/US stratum appear to be down
No idea, im on EU. Are you sure its down? Can anyone else confirm this? |
|
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
rsx19
|
|
May 23, 2014, 07:28:18 AM |
|
CA/US stratum appear to be down
No idea, im on EU. Are you sure its down? Can anyone else confirm this? yup seems down for me too |
BlackCoin For poor Shibe - BMobXjx9TN96a1qmZA9pSSzJur6UH9PWgU
|
|
|
suchmoon
Legendary
 Offline
Activity: 3654
Merit: 8921
https://bpip.org
|
|
May 23, 2014, 07:30:32 AM |
|
CA/US stratum appear to be down
No idea, im on EU. Are you sure its down? Can anyone else confirm this? yup seems down for me too Yes, same here. |
|
|
|
|
|
Terk (OP)
|
|
May 23, 2014, 08:31:41 AM |
|
The US server is back online.
It was down due to unexpected tech issues, and for some reason my monitoring alerts was delivered to my phone with 2 hours delay. I'm sorry for the downtime.
|
|
|
|
|
gtraah
|
|
May 23, 2014, 09:38:31 AM |
|
Quick question -
EXAMPLE ONLY
1st Pool has 165ms Ping and [Avg 24hr --104% LTC Profitabilty] 2%fee 1-2% Rejection
2nd Pool has 235ms Ping and [Avg 24hr --117% LTC Profitabilty] 2%fee 4-6% Rejection
Which do you think will pay out more?
|
|
|
|
|
|
Ibistru
|
|
May 23, 2014, 09:53:09 AM |
|
Quick question -
EXAMPLE ONLY
1st Pool has 165ms Ping and [Avg 24hr --104% LTC Profitabilty] 2%fee 1-2% Rejection
2nd Pool has 235ms Ping and [Avg 24hr --117% LTC Profitabilty] 2%fee 4-6% Rejection
Which do you think will pay out more?
You just need to calculate net profitability, i.e. excluding rejections and fees. net profitability = gross profitability x (1-fee) x (1-rejections) For your example (I will average the rejection rate): 1st: 104⋅(1−0.02)⋅(1−0.015) = 100.3912 2nd: 117⋅(1−0.02)⋅(1−0.05) = 108.927 In this case the second pool WAS more profitable in the observed period. I uppercased 'was' because past profitability is in no way a prediction for future profitability. One pool can have 120% LTC profitability in a given hour and 80% prof. in the following hour. It is just luck. Rejection rates are more stable tough, so try to avoid pools where you get high rejections. |
|
|
|
|
|
Terk (OP)
|
|
May 23, 2014, 10:17:04 AM |
|
All CM published numbers are after fees, so you don't need to subtract a fee from them because you would do it twice.
Speaking of rejects, does anyone using the US server notice any change in rejects and/or accepted MHs on the new server launched an hour ago?
|
|
|
|
|
gtraah
|
|
May 23, 2014, 10:36:21 AM |
|
Quick question -
EXAMPLE ONLY
1st Pool has 165ms Ping and [Avg 24hr --104% LTC Profitabilty] 2%fee 1-2% Rejection
2nd Pool has 235ms Ping and [Avg 24hr --117% LTC Profitabilty] 2%fee 4-6% Rejection
Which do you think will pay out more?
You just need to calculate net profitability, i.e. excluding rejections and fees. net profitability = gross profitability x (1-fee) x (1-rejections) For your example (I will average the rejection rate): 1st: 104⋅(1−0.02)⋅(1−0.015) = 100.3912 2nd: 117⋅(1−0.02)⋅(1−0.05) = 108.927 In this case the second pool WAS more profitable in the observed period. I uppercased 'was' because past profitability is in no way a prediction for future profitability. One pool can have 120% LTC profitability in a given hour and 80% prof. in the following hour. It is just luck. Rejection rates are more stable tough, so try to avoid pools where you get high rejections. But wait a minute, what about the Ping doesn't this affect accepted shares also?? Edit: New server I hear??! Hmmm must try this soon hopefully rejects drop |
|
|
|
|
|
Terk (OP)
|
|
May 23, 2014, 10:39:17 AM |
|
But wait a minute, what about the Ping doesn't this affect accepted shares also??
Ping time is one of the reasons causing rejected shares. You don't need to include it in your calculations as it's already “included” in reject ratio. |
|
|
|
|
gtraah
|
|
May 23, 2014, 10:41:27 AM
Last edit: May 23, 2014, 11:01:06 AM by gtraah |
|
But wait a minute, what about the Ping doesn't this affect accepted shares also??
Ping time is one of the reasons causing rejected shares. You don't need to include it in your calculations as it's already “included” in reject ratio. But the interesting thing about this is, I have had reject rates higher with certain pools with ping around the same. Example - 1 pool 230ms = 6% reject 2 pool 230ms = 3% reject Ahh Ok I think I see what you mean..... All you need to look at in calculations is Accepted - Rejected... Ping can be what ever it wants ? DOHH |
|
|
|
|
|
gtraah
|
|
May 23, 2014, 11:10:59 AM |
|
Where are your servers located? Have you ever thought of adding new servers in different areas around the globe? Oceania which will cover, most Asia/Australia etc....
Also I am guessing your servers are on the East coast of US?
Even West coast would be another good option I think as waffle USWEST pings are close to their Oceania server ping... 177ms vs 164ms
Comparing to waffle EAST & US CLEVER @ 238-237ms Most likely same region
|
|
|
|
|
|
schnebi
|
|
May 23, 2014, 02:59:06 PM |
|
I am mining with two gridseed G-Blade. It starts really good, but after half an hour the pool difficulty rises to 2335!! and i don't get a single share anymore. What can I do?
|
|
|
|
|
|
Terk (OP)
|
|
May 23, 2014, 03:12:52 PM |
|
I am mining with two gridseed G-Blade. It starts really good, but after half an hour the pool difficulty rises to 2335!! and i don't get a single share anymore. What can I do?
It might be because your rig was extremely lucky and got too many shares within a short time frame. Even if difficulty changed to 2335 it should change back down within couple of minutes. Can you tell me your username? I'll monitor it and see how it's working. |
|
|
|
|
schnebi
|
|
May 23, 2014, 03:18:50 PM |
|
I am mining with two gridseed G-Blade. It starts really good, but after half an hour the pool difficulty rises to 2335!! and i don't get a single share anymore. What can I do?
It might be because your rig was extremely lucky and got too many shares within a short time frame. Even if difficulty changed to 2335 it should change back down within couple of minutes. Can you tell me your username? I'll monitor it and see how it's working. My Username is : 1ExxrRYFVqFiT2PiUQppsxhk5aSBYAuEyT But I just restartet my rig, so the diifficulty is down to 512 now. But I already tried a few times and the difficulty always rises after a few minutes. And I waited for like 45 Minutes and it didnt went back down. Edit: Its already up to 1990 after 2 Minutes |
|
|
|
|
|
schnebi
|
|
May 23, 2014, 03:34:59 PM |
|
I am mining with two gridseed G-Blade. It starts really good, but after half an hour the pool difficulty rises to 2335!! and i don't get a single share anymore. What can I do?
It might be because your rig was extremely lucky and got too many shares within a short time frame. Even if difficulty changed to 2335 it should change back down within couple of minutes. Can you tell me your username? I'll monitor it and see how it's working. But it seems not to be corresponding with the gigh difficulty. I had Diff above 4000 a few minutes ago and i even got accepted share. It seems like after approximately half an hour no share is accepted anymore |
|
|
|
|
quakefiend420
Legendary
Offline
Activity: 784
Merit: 1000
|
|
May 23, 2014, 04:10:09 PM |
|
I am mining with two gridseed G-Blade. It starts really good, but after half an hour the pool difficulty rises to 2335!! and i don't get a single share anymore. What can I do?
It might be because your rig was extremely lucky and got too many shares within a short time frame. Even if difficulty changed to 2335 it should change back down within couple of minutes. Can you tell me your username? I'll monitor it and see how it's working. But it seems not to be corresponding with the gigh difficulty. I had Diff above 4000 a few minutes ago and i even got accepted share. It seems like after approximately half an hour no share is accepted anymore I was at 19000 just a minute ago, it's screwing with my auto-restart cause my miner thinks that blades are going down when in actuality it's just taking a long time to solve a share. What happened to fixed diff at 512? |
|
|
|
|
|
schnebi
|
|
May 23, 2014, 04:27:16 PM |
|
I am mining with two gridseed G-Blade. It starts really good, but after half an hour the pool difficulty rises to 2335!! and i don't get a single share anymore. What can I do?
It might be because your rig was extremely lucky and got too many shares within a short time frame. Even if difficulty changed to 2335 it should change back down within couple of minutes. Can you tell me your username? I'll monitor it and see how it's working. But it seems not to be corresponding with the gigh difficulty. I had Diff above 4000 a few minutes ago and i even got accepted share. It seems like after approximately half an hour no share is accepted anymore I was at 19000 just a minute ago, it's screwing with my auto-restart cause my miner thinks that blades are going down when in actuality it's just taking a long time to solve a share. What happened to fixed diff at 512? Yes, i would also like to have fixed diff at 512! I thinl this is really a nice Pool. I like it more than other Multicoin Pools. For now its running smooth for nearly an hour or so, but its not good if you don't know if it stops workinng in a moment when you're not looking at it for a couple of hours... |
|
|
|
|
|
byt411
|
|
May 23, 2014, 04:36:16 PM |
|
I am mining with two gridseed G-Blade. It starts really good, but after half an hour the pool difficulty rises to 2335!! and i don't get a single share anymore. What can I do?
It might be because your rig was extremely lucky and got too many shares within a short time frame. Even if difficulty changed to 2335 it should change back down within couple of minutes. Can you tell me your username? I'll monitor it and see how it's working. But it seems not to be corresponding with the gigh difficulty. I had Diff above 4000 a few minutes ago and i even got accepted share. It seems like after approximately half an hour no share is accepted anymore I was at 19000 just a minute ago, it's screwing with my auto-restart cause my miner thinks that blades are going down when in actuality it's just taking a long time to solve a share. What happened to fixed diff at 512? Yes, i would also like to have fixed diff at 512! I thinl this is really a nice Pool. I like it more than other Multicoin Pools. For now its running smooth for nearly an hour or so, but its not good if you don't know if it stops workinng in a moment when you're not looking at it for a couple of hours... Hm. So before, people complained about not having vardiff, and then that there is fixed difficulty. Now, one 512 share = 512, one 1 share = 1, one 1024 share = 1024. So 512 difficulty one shares equal 512. If you still don't understand, it means that there is no difference. |
|
|
|
|
quakefiend420
Legendary
Offline
Activity: 784
Merit: 1000
|
|
May 23, 2014, 05:34:34 PM |
|
I am mining with two gridseed G-Blade. It starts really good, but after half an hour the pool difficulty rises to 2335!! and i don't get a single share anymore. What can I do?
It might be because your rig was extremely lucky and got too many shares within a short time frame. Even if difficulty changed to 2335 it should change back down within couple of minutes. Can you tell me your username? I'll monitor it and see how it's working. But it seems not to be corresponding with the gigh difficulty. I had Diff above 4000 a few minutes ago and i even got accepted share. It seems like after approximately half an hour no share is accepted anymore I was at 19000 just a minute ago, it's screwing with my auto-restart cause my miner thinks that blades are going down when in actuality it's just taking a long time to solve a share. What happened to fixed diff at 512? Yes, i would also like to have fixed diff at 512! I thinl this is really a nice Pool. I like it more than other Multicoin Pools. For now its running smooth for nearly an hour or so, but its not good if you don't know if it stops workinng in a moment when you're not looking at it for a couple of hours... Hm. So before, people complained about not having vardiff, and then that there is fixed difficulty. Now, one 512 share = 512, one 1 share = 1, one 1024 share = 1024. So 512 difficulty one shares equal 512. If you still don't understand, it means that there is no difference. If the difficulty is getting so high over time that a miner can't solve a share before it's stale, that's a problem. |
|
|
|
|
|
byt411
|
|
May 23, 2014, 05:38:10 PM |
|
I am mining with two gridseed G-Blade. It starts really good, but after half an hour the pool difficulty rises to 2335!! and i don't get a single share anymore. What can I do?
It might be because your rig was extremely lucky and got too many shares within a short time frame. Even if difficulty changed to 2335 it should change back down within couple of minutes. Can you tell me your username? I'll monitor it and see how it's working. But it seems not to be corresponding with the gigh difficulty. I had Diff above 4000 a few minutes ago and i even got accepted share. It seems like after approximately half an hour no share is accepted anymore I was at 19000 just a minute ago, it's screwing with my auto-restart cause my miner thinks that blades are going down when in actuality it's just taking a long time to solve a share. What happened to fixed diff at 512? Yes, i would also like to have fixed diff at 512! I thinl this is really a nice Pool. I like it more than other Multicoin Pools. For now its running smooth for nearly an hour or so, but its not good if you don't know if it stops workinng in a moment when you're not looking at it for a couple of hours... Hm. So before, people complained about not having vardiff, and then that there is fixed difficulty. Now, one 512 share = 512, one 1 share = 1, one 1024 share = 1024. So 512 difficulty one shares equal 512. If you still don't understand, it means that there is no difference. If the difficulty is getting so high over time that a miner can't solve a share before it's stale, that's a problem. No it's not, because stales are also paid for. |
|
|
|
|
|
