payments sent
I think I'm going to shut this down -- compatibility with virtually all pools has broken, and multiclone just isn't a profitable way to mine anymore since I don't have time to fix it.
Topic: del (Read 16660 times)
Hey nick, I know you don't know all the answers.. But you've been pretty good at it so far.
I thought because the price had dropped so low, we would mine more, but it was considerably less. Why is that?
Also, when I suggested to mine just on solo, I meant until we get the block and then go back to normal. I didn't mean forever.
I thought because the price had dropped so low, we would mine more, but it was considerably less. Why is that?
Also, when I suggested to mine just on solo, I meant until we get the block and then go back to normal. I didn't mean forever.
Solo mining:
Would it be beneficial if you set everyone to mine on the solo? I mean, if a block was achieved with us, then that could be quite a few coins right?
Would it be beneficial if you set everyone to mine on the solo? I mean, if a block was achieved with us, then that could be quite a few coins right?
All that would accomplish is turn multiclone into Yet Another Proportional Pool. Pointless. Solo is there so that workers do something quasi-useful when the pool can't give it anything better. There's still a chance we'll find something on solo mining, which is why we do that rather than miners idling.
Also, the getwork daemon died and prevented any work getting distributed earlier today due to a perl threading issue from the original code that it looks like the original Multipool was fighting with, too. I think I fixed it, but it's happened before and I thought I fixed it that time too.
This time, I wrote some code to just relaunch the damn threads when they crash. Things should be working again, and this should provide some better stability than 'lets hope Nick notices the server is messed up and manually restarts it'
The pool seems to be solo mining a lot. The majority of my shares from today have gone into solo mining. Why not put them into eligius or something like that instead?
Solo happens in the following 2 conditions:
* the target pools don't give multiclone enough work quickly enough to distribute to its users to prevent 'miner idle's
* a multiclone user's miner is misbehaving (hasn't been submitting enough valid shares relative to the getworks requested)
That said, for the past ~day, we've only got ~3% stale and ~3% solo.
Code:
bash-4.1$ grep "submitting share.*" log/037 | wc -l
101286
bash-4.1$ grep "submitting share.*incorrect" log/037 | wc -l
3215
bash-4.1$ grep "submitting share.*solo" log/037 | wc -l
2998
With a 1.25 efficiency (of the confirmed shares, which is what my new miner has got for the past week since the problems were resolved), you still come out (1-.03-.03)*1.25 = 1.175 -> 17.5% ahead of the 'ideal' non-hopping case.
I have some ideas on things that might help reduce solo that I might get to this weekend...
Mining is fine.
Checking stats isn't: "Unable to connect" in browser. Anyone else unable to see the stats page?
Checking stats isn't: "Unable to connect" in browser. Anyone else unable to see the stats page?
Fixed. Divide-by-zero error crashed the website.
Only the coolest of the cool can divide by zero.
Also, what happens when the solo gets a block? Is it just distributed among you and us?
Mining is fine.
Checking stats isn't: "Unable to connect" in browser. Anyone else unable to see the stats page?
Checking stats isn't: "Unable to connect" in browser. Anyone else unable to see the stats page?
Fixed. Divide-by-zero error crashed the website.
I had increased Multiclone's work pool queue yesterday to try to deal with the idles (which were caused by the problematic user). Unfortunate side effect of this seems to be increased stales. I put the work queue back where it was before. Give it a shot again, and things should be back to how they were before?
I gave it another go and I'm afraid it's still very high.Grand Total : [1049.77 MHash/sec] [164 Accepted] [16 Rejected] [9.756% Rejected]
This integration of the solo pool as a backup (with blocking calls! one malfunction and everything is borked!) causes more trouble than anything else... My local bitcoind flaked out and needed restarted, so the pool crashed for about 30 minutes just a little bit ago.
Have a couple different longpoll push mechanisms to try that can hopefully fix the stales issue.
I had increased Multiclone's work pool queue yesterday to try to deal with the idles (which were caused by the problematic user). Unfortunate side effect of this seems to be increased stales. I put the work queue back where it was before. Give it a shot again, and things should be back to how they were before?
I gave it another go and I'm afraid it's still very high.Grand Total : [1049.77 MHash/sec] [164 Accepted] [16 Rejected] [9.756% Rejected]
Ah right, I'd forgotten about that. And you seem to be the only one with that particular quirky problem. I'll pay you out manually in the next day or two.
I don't know if I have the same quirky problem, but I'm still waiting from my payout from more than 3 weeks ago:
http://multiclone.us.to:18080/user/?address=18jkF8XQHRPoNYfJKFNWnfT4Xz2sAEwkb7
http://multiclone.us.to:18080/user/?address=1GxYHKL445GiyXa2XHpQHzDqr4ixeemSSB
http://multiclone.us.to:18080/user/?address=1B5dUoXDzF1EamzxLejWW2Z7uty5VepYff
May you look into that?
Thanks.
I'm currently getting a lot of stales. Known issue?
What are you calling 'a lot'? global rate for past ~day is around 3.5%, which is certainly higher than normal, but not ridiculously high.
I think it's likely due to the problem user my previous post describes.
Edit: Just mined for a little over 20 minutes and got this:
Grand Total : [1049.11 MHash/sec] [308 Accepted] [35 Rejected] [11.363% Rejected]
I had increased Multiclone's work pool queue yesterday to try to deal with the idles (which were caused by the problematic user). Unfortunate side effect of this seems to be increased stales. I put the work queue back where it was before. Give it a shot again, and things should be back to how they were before?
I'm currently getting a lot of stales. Known issue?
What are you calling 'a lot'? global rate for past ~day is around 3.5%, which is certainly higher than normal, but not ridiculously high.
I think it's likely due to the problem user my previous post describes.
Edit: Just mined for a little over 20 minutes and got this:
Grand Total : [1049.11 MHash/sec] [308 Accepted] [35 Rejected] [11.363% Rejected]
Got my bitcoins.lc payout - thanks Nick!
Just 16000 shares on btcmine to go...
Ah right, I'd forgotten about that. And you seem to be the only one with that particular quirky problem. I'll pay you out manually in the next day or two.Just 16000 shares on btcmine to go...
No worries - and I'm not hassling mind. I know running a pool part time must be a pain.
Jump to: