Yeah. I remember that. I was just hoping he would share his C with us (well... me actually ). C=300
|
|
|
I have been running at a consistant total M/Hash average for around a week now and in that time the pool's rate has risen 80 G/Hashes in that time, however my payouts seem to have stayed steady.
You're right, once the pool find at least few blocks per day (say 15 blocks and more), people should get very steady payout, total pool hashrate is not relevant.
|
|
|
The slower miners will get their shares in the next round. "Sweet spot" is a myth.
Amen.
|
|
|
Hey slush, out of curiosity, do you ever intend to pay for invalid blocks like Tycho?
I prefer lower fees and following bitcoin rules, so - no.
|
|
|
ok this ain't right. I refresh my profile page to look at the numbers every now and then when I'm on the computer. I know a round is over when my total creeps up a little bit then I'll look at the stats page to see how much I got for that round since it'll vary because I'm using the comp. Twice today I saw my total actually decline. Any reason that's happening Slush?
Only reason for declining total reward is invalid block or payout. Nothing else.
|
|
|
Adding up those rewards yields 0.53864479. But I've only got a confirmed reward of 0.31948031.
Confirmed blocks are processed (moved from unconfirmed to confirmed on profile page) once per hour, but stats is online. This is reason why those sums may differ.
|
|
|
A. extract my payments....I have 2 BTC that are confirmed
You have to fill your wallet address on pool profile page. And use "Getting started" page mentioned above to get your wallet address...
|
|
|
Immune, your round reward is not important. With higher pool hashrate, round rewards go slightly down, but you're getting them more often. So definitely no reason to worry about. For very short rounds your reward can have slightly higher variance, but it also averages out after some time. Everything around mining is highly probabilistic, stop watching separate rounds and start watching statistics for longer time period .
|
|
|
Database migration done. Pool didn't fall, so maybe (maybe!) all those changes helped.
|
|
|
OK, I made some changes yesterday, so I'm going to watch if it helped; 10.00 UTC is soon. There will be short downtime even if it don't fall itself, because I'll migrate DB (which I didn't want to do yesterday, because of one extra downtime).
|
|
|
Slush have you considered switching to a provider such as Rackspace or Softlayer?
Yes, I'm thinking about them as alternative to Linode. Another provider to consider may be iWeb. They're Canadian based, but when I had a dedicated server with them I found them to have a very reliable network.
We have ~30 servers in iWeb and as far as I can say, their support is horrible. For example - waiting two days for connecting console to server? Really?
|
|
|
Slush, forgive me for speaking out of line here but isn't it about time you invested in some real dedicated machines for your pool and not cheap VPS solutions?
This is of course valid question. I'm Linode customer for many years and I have so far great experience with them. I don't think it is 'cheap VPS solution', it is just 'VPS solution'. Problems happen everywhere, for example one my real rack server catched up by fire before few months. 'real == better' isn't valid in every situation. VPS is very good solution for application like pool, because I can scale it as I wish. Pool went from single server with 512MB RAM (on 16. December) to many server infrastructure with standalone database, balancer with possible IP failover, many backends where I can disconnect any of them without pool outage and so on. Everything that with 15 minute planned outage because of database migration. In case of rising demand, I can make pool infrastructure 10x stronger by few clicks. This is not possible with real servers. I hope that we'll find reason for those issues, and I'm really sorry for it; we're trying to do the best. But if we won't find any trouble, I'm of course ready to migrate to another provider to give best possible pool experience.
|
|
|
Reward for block 4753 isn't correct because block was finished during outage, I will recalculate it later...
|
|
|
It may be helpful that while the server malfunctions refreshing the web page results often: "Error 502 - bad gateway"
Edit: or "Error 504 - gateway timeout."
I know that, it was because I tried to restart everything, including website. Unfortunately nothing helped :-/
|
|
|
yeah thats weird bro. I have been watching it too every day around this time. Are you sure the server does not do any maintenance tasks at this time of day?
There are of course no cronjobs on my servers. But as servers are virtual, it might be caused by heavy maintenance of *other* machines. Or perhaps your uplink does?
Uplink works well, I see normal traffic here.
|
|
|
So what time does it usually fix itself?
All three days it failed at 10:05 UTC +- few minutes. Then recover for few minutes around 10:30, then fall down again and looks like finally started working after 11:00. Of course tried to restart everything and watch everything, including possibly malicious traffic on external interfaces (getwork and bitcoin p2p), but everything looks normally. It is just incredibly laggy at this time, so 99% of requests fail on timeouts. It might be related to weekend infrastructure update, when all server plans were updated (and severs were physically moved to another machines). I requested moving all servers to another locations, maybe it helps. If it will repeat tomorrow, I'll change provider...
|
|
|
I don't think so... this is the 3rd day when the server drops at around this same hour. It will pick up in half an hour or so. slush said he will ask the provider what's going on. Hope he finds out.
I was watching today's outage whole time, with another sysadmin. We didn't found anything wrong with application, but internal routing looks corrupted. It is crazy that it is always at the same time and after some time it recover itself. Linode guys are saying that everything works on their side, but I'm now absolutely sure that those issues are related to infrastructure. So I'm forced to change provider, which unfortunately will take some time.
|
|
|
It would be nice if you could make a short formula to make an approximate calculation of how much users can be paid over the course of 24 hours, with a few variables incl. # shares/hour, current reward per round, etc...
There should be no significant difference between pool mining and standalone mining (well, except 2% fee). So feel free to use standard bitcoin calculator. Shares, rounds, score system etc are just tools to track proof of works of individual users in pool...
|
|
|
I am still having problems connecting. Are there still any on going issues?
Actually don't know about anything... site works for you?
|
|
|
22/05/2011 14:00:56
Well, it was yesterday, right? Then it is OK because I finished infrastructure changes. I meant that it appeared today, that's why I was surprised.
|
|
|
|