Topic: [CLOSED] MtRed (PPS, LP+, API, 0 FEE) STRATUM on mine.mtred.com:3333 - page 44. (Read 176141 times)
February 21, 2012, 09:26:17 AM
8837 seems to have higher reject for the last day or two. They were exceptionally low, and the rate still looks good so far, but the average is still climbing. The average I refer to is from a session started about 96 hours ago, and it has nearly doubled in the last 36 hours. Is load getting significantly higher on 8837 as it was on 8337 last time I asked about rejects?
February 19, 2012, 01:15:45 PM
I think the server that is hosting everything crashed. Website is down, and pool is down.
Something happened to cause a complete reboot about 2 hours ago. I'm not sure what tho, I'll be around all day monitoring the server.
February 19, 2012, 12:42:54 PM
I think the server that is hosting everything crashed. Website is down, and pool is down.
February 19, 2012, 02:30:07 AM
Hashrate is up to about 105GH/s
February 17, 2012, 01:27:36 PM
Ok Some changes in some stuff. Should be lightning! Let me know how it comes.
Thanks,
RR
Thanks,
RR
God damn, what was the problem? Sitting at about 150 Accepted 0 Rejected, LP is working, and no more work related errors. Whatever you did, great fucking job!
Always glad to make Tittiez happy
February 17, 2012, 08:05:56 AM
Ok Some changes in some stuff. Should be lightning! Let me know how it comes.
Thanks,
RR
Thanks,
RR
God damn, what was the problem? Sitting at about 150 Accepted 0 Rejected, LP is working, and no more work related errors. Whatever you did, great fucking job!
February 17, 2012, 07:53:45 AM
Are we ever going to see LTC mining on this pool?
February 17, 2012, 12:49:48 AM
Ok Some changes in some stuff. Should be lightning! Let me know how it comes.
Thanks,
RR
Thanks,
RR
February 17, 2012, 12:36:53 AM
Ok, I'm looking into the LP problems; will report back asap.
February 16, 2012, 10:58:55 PM
Getting "Pool not providing work fast enough" very often.
Can you try port 8837?
I am using port 8837. Sitting at 755 Accepted and 37 Rejected (About 5% Rejects, Meh). I am also having LP Problems, and cgminer detects the new block itself after a few rejects (same as @The00Dustin)
Edit:
Caught it fucking up in action:
February 16, 2012, 09:57:42 PM
My experience with 8837 thus far is rejects are better than 8337 but I haven't seen any LPs. So far (when I've been looking) cgminer detects a new block after a reject or two pretty consistently. It says it is connected with LP, but I don't seem to be getting them.
February 16, 2012, 09:16:34 PM
Getting "Pool not providing work fast enough" very often.
Can you try port 8837?
February 16, 2012, 08:44:03 PM
Getting "Pool not providing work fast enough" very often.
February 16, 2012, 03:14:38 PM
Minor Correction: the block on the 5th was ~5 days going.
The invalid block was also pretty big at over a day in time and 2523897 shares paying over 90BTC for an orphaned block.
The invalid block was also pretty big at over a day in time and 2523897 shares paying over 90BTC for an orphaned block.
February 16, 2012, 02:44:01 PM
The block that was solved on the 5th (a week or so long) we paid out almost 300BTC.
Ouch! I clearly misinterpreted the quote from February 7th, may luck be with your pool! February 16, 2012, 02:34:54 PM
I understand what you are doing, and I don't have a problem with it (although removing the confirmation code and paying sooner out of found blocks would be nice). As it stands, I think the proper term is SMPPS, and can work fine (although the additional stats arsbitcoin provides on that are potentially useful). If I am wrong and you will be paying for shares that add up to more than 50BTC when a block is found and confirmed, then maybe your explanation is right, but in that case, I hope you have a nice buffer for the bad luck. I have seen comments that to be safe running a pure pps pool one needs to have a buffer in the thousands of BTC. ARS would be currently be -573 BTC if they were doing pure instead of shared maximum. Also, I will try 8837 and see if rejects are better.
Ohh then yes, we pay out more than 50BTC on unlucky blocks (unlucky being more than the difficulty to solve a block). The block that was solved on the 5th (a week or so long) we paid out almost 300BTC. SMPPS was an option when we were looking at alternative reward methods, but I believe miners like the full pps value for every share.
February 16, 2012, 02:27:23 PM
I understand what you are doing, and I don't have a problem with it (although removing the confirmation code and paying sooner out of found blocks would be nice). As it stands, I think the proper term is SMPPS, and can work fine (although the additional stats arsbitcoin provides on that are potentially useful). If I am wrong and you will be paying for shares that add up to more than 50BTC when a block is found and confirmed, then maybe your explanation is right, but in that case, I hope you have a nice buffer for the bad luck. I have seen comments that to be safe running a pure pps pool one needs to have a buffer in the thousands of BTC. ARS would be currently be -573 BTC if they were doing pure instead of shared maximum. Also, I will try 8837 and see if rejects are better.
February 16, 2012, 02:02:32 PM
I see what you are saying about that waiting period and the fact we pay out on block not shares, its a artifact from when we where prop.
We still pay a pure-pps value, the only difernce is that we pay after the block is found, it should all be the same reward just a little longer of a delay.
We need this time buffer for when luck gets really bad. We haven't had an orphaned block in a while (since we switched to pps) so there was never a urge to update the block of code.
For stales, Try mining on the beta port: 8837
The problem is the load of CPU miners that are on MtRed are taking a good while to loop through all of them notifying of a new block.
The beta pool should alleviate that some.
We still pay a pure-pps value, the only difernce is that we pay after the block is found, it should all be the same reward just a little longer of a delay.
We need this time buffer for when luck gets really bad. We haven't had an orphaned block in a while (since we switched to pps) so there was never a urge to update the block of code.
For stales, Try mining on the beta port: 8837
The problem is the load of CPU miners that are on MtRed are taking a good while to loop through all of them notifying of a new block.
The beta pool should alleviate that some.
February 16, 2012, 06:36:39 AM
PPS rate is on https://mtred.com. However, I'm not sure "pure PPS" is the right term. Why?
This:
On a side note, I was also getting rather high rejects with cgminer last I checked...
This:
Some bad luck this week, long blocks and an orphan BTC block.
I want everyone to know that rewards will roll into this or the next block.
Makes it look like if shares > difficulty, you don't get paid yet (which would be like Ars, SMPPS). Also the interface still makes it look like blocks have to be confirmed before you can get paid (which is technically paying for blocks, not shares). I'm not saying either of these things is necessarily a bad deal, just that I'm not sure it's "Pure PPS".I want everyone to know that rewards will roll into this or the next block.
On a side note, I was also getting rather high rejects with cgminer last I checked...
February 16, 2012, 04:41:21 AM
I just put one of my miner to work at your pool. and got a question.
how long is the delay for the dashboard update? or how often does it update with the stats?
where can i check the PPS rate?
how long is the delay for the dashboard update? or how often does it update with the stats?
where can i check the PPS rate?
Jump to: