Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 1122. (Read 4382769 times)
February 09, 2011, 07:20:07 PM
Hypothetically speaking, if I made available 25, modern dual processor, quad core, servers for 2 hours per day, roughly how many, on average, bitcoins could be expected from joining this pool?
February 09, 2011, 02:06:45 PM
In case you need it, check midphase.com server plans.
Thanks gusti for the tip. I have few boxes on Linode and I love the service and their support, so I'd like to stay here. I also think we've fixed the network issue, so no need to migration right now. Keep in mind that those 160 requests/s (10.000.000.000 requests per month!) are pretty high traffic and everything must be perfect to run smoothly on VPS.
February 09, 2011, 02:01:26 PM
I'm having some connection problems, quite regularly a connection is lost every 7-10 minutes, is it just me?
After discussing it with server support and little fiddling with server, I think it should be better now. Can you confirm that?
February 09, 2011, 11:11:24 AM
I'm having some connection problems, quite regularly a connection is lost every 7-10 minutes, is it just me?
If you see connection timeouts, I'm solving this. looks like network is shaped. I'll try to upgrade my server today. If it does not help, I'll contact server support for some help.
In case you need it, check midphase.com server plans.
Nice network, price and support.
I have servers with 2 yrs uptime with them.
February 09, 2011, 11:02:44 AM
I'm having some connection problems, quite regularly a connection is lost every 7-10 minutes, is it just me?
If you see connection timeouts, I'm solving this. looks like network is shaped. I'll try to upgrade my server today. If it does not help, I'll contact server support for some help.
February 09, 2011, 09:21:34 AM
It is below _average_ pool capacity. When new block arrive, there are many seconds with significant lower (effective) hashrate. There is also significant variance in share submitting rate. Sometimes there are almost 20 shares per second, sometimes there is almost nothing. And I don't see any trouble with stale block algorithm itself.
That's random for you 
I'm having some connection problems, quite regularly a connection is lost every 7-10 minutes, is it just me?
February 09, 2011, 08:58:28 AM
Only 3 shares is below 0.5s of the pool capacity.
It is below _average_ pool capacity. When new block arrive, there are many seconds with significant lower (effective) hashrate. There is also significant variance in share submitting rate. Sometimes there are almost 20 shares per second, sometimes there is almost nothing. And I don't see any trouble with stale block algorithm itself.
February 09, 2011, 08:33:16 AM
Stale shares are around 1-2%. Of course there were many stale shares in this round, but it is how it works. Calculating stale shares is not fair, because people get reward for something which cannot give valid block to pool. It also improved overall pool performance, because some people had strange miner settings (ask rate over 180 seconds etc).
I'm not advocating counting stale shares but I was curious how many stale shares arrived within the same timeframe. It can show the delay inefficiencies.
Quote
So 7 seconds for three shares at the beginning of round seems to be fine.
I would expect more. With 5s getwork refresh time, most of the workers should have worked on the non-stale block at least some of their time. Some of the workers should have worked most of this time. Only 3 shares is below 0.5s of the pool capacity. I would expect 10-20 shares.
February 09, 2011, 07:25:39 AM
But the round took 7 seconds to complete and the pool should have made 52 shares at this time frame. Poor those who earned a stale share at that time. How many stale shares did you log during this round (and on average during all rounds)?
Stale shares are around 1-2%. Of course there were many stale shares in this round, but it is how it works. Calculating stale shares is not fair, because people get reward for something which cannot give valid block to pool. It also improved overall pool performance, because some people had strange miner settings (ask rate over 180 seconds etc).
So 7 seconds for three shares at the beginning of round seems to be fine.
February 09, 2011, 06:30:22 AM
Btw. the pool need only 3 shares to found block 106959 yesterday. Congratulation for all three users, which get 16.6 BTC for one share! :-)
But the round took 7 seconds to complete and the pool should have made 52 shares at this time frame. Poor those who earned a stale share at that time. How many stale shares did you log during this round (and on average during all rounds)?
February 09, 2011, 05:49:50 AM
Btw. the pool need only 3 shares to found block 106959 yesterday. Congratulation for all three users, which get 16.6 BTC for one share! :-)
February 09, 2011, 05:43:33 AM
Why everything changed?
Read this forum for few posts back. It will be back soon.
February 09, 2011, 05:01:39 AM
Why everything changed?
I mean before it will show how many shares i mined ...
Now many things not showing.
I mean before it will show how many shares i mined ...
Now many things not showing.
February 05, 2011, 08:48:26 PM
I really enjoyed seeing some of my customers on the top.
Maybe us GPU miners should make a hall of fame, too? My miners found a total of 1184 blocks and I guess ArtForz's found even more; not to mention all those CPU miners running a year ago.
February 05, 2011, 07:23:20 PM
So it's been changed back to how it was.
No, nothing changed. It is how it works all the time. You mixed it with jgarzik's pool, which worked like you're talking.
February 05, 2011, 07:21:47 PM
No server accept shares for whole round, not only for current block.
So it's been changed back to how it was. The server accepts shares for the current round, even if the block count changed by 1?
Any old work from previous rounds are ignored?
February 05, 2011, 07:19:00 PM
I've updated my miner to reduce share loss in pool situations. Update to newest.
Thank you.
February 05, 2011, 07:14:59 PM
All this crap to try and prevent "fraud". Delaying/removing stats doesn't stop that BTW.
Tell me the reason why not. (well, I know it, but I bet you don't.)
Quote
The server already only accepts shares for current blocks, but what you've done is overkill, plain and simple.
No server accept shares for whole round, not only for current block.
February 05, 2011, 06:46:17 PM
Damn, I leave for 1 week, come back and the server stats are totally different and gone.
All this crap to try and prevent "fraud". Delaying/removing stats doesn't stop that BTW.
The server already only accepts shares for current blocks, but what you've done is overkill, plain and simple.
Time for a new pool server to be born, cause this just blows now.
All this crap to try and prevent "fraud". Delaying/removing stats doesn't stop that BTW.
The server already only accepts shares for current blocks, but what you've done is overkill, plain and simple.
Time for a new pool server to be born, cause this just blows now.
February 05, 2011, 02:42:31 PM
You still didn't find any solution how to find, that pool found a block, which makes "43% cheating" impossible.
I think all you really need to is to estimate the compute power of the pool to work out expected time for 43.5% (as of writing that is about 23 minutes). If you switched to working solo after an average-43.5% duration and worked solo until the average block-find time (as of writing that is about 40 minutes), then your miner's average performance should still exceed the performance of full-time pool mining. Although, I haven't done the math to work out the expected pay-off of that strategy, so maybe I am wrong.
Jump to: