Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 231. (Read 903150 times)
September 29, 2013, 12:55:36 PM
You just had to go clicking buttons, didn't you! Now look what you've done. Time to sell more Block Erupters (now 0.15 BTC shipping included) to make up for this.
September 29, 2013, 12:50:34 PM
.............. What's that button for...........
That's the button you click to change the pool luck.
You didn't press it did you?!?!?!
Oh, damn. Sorry.... I just wondered what it did. Quick - How do you un-click it? Is it a toggle?
Dunno?
I wonder if it's part of the 51% Mitigation plan?
September 29, 2013, 12:35:48 PM
.............. What's that button for...........
That's the button you click to change the pool luck.
You didn't press it did you?!?!?!
Oh, damn. Sorry.... I just wondered what it did. Quick - How do you un-click it? Is it a toggle?
September 29, 2013, 12:14:11 PM
.............. What's that button for...........
That's the button you click to change the pool luck.
You didn't press it did you?!?!?!
September 29, 2013, 12:06:41 PM
.............. What's that button for...........
That's the button you click to change the pool luck.
You didn't press it did you?!?!?!
September 29, 2013, 12:02:12 PM
.............. What's that button for...........
September 29, 2013, 11:50:54 AM
It seems as of we are now paying for that long good luck steak on blocks early in the difficulty change. 
September 29, 2013, 10:27:14 AM
Another item that got kicked to the side for a while has finally been checked off the To-Do list. PPLNS Earnings History now has a CSV export available on the settings page. This means you now have a CSV export available for all earnings and payout data.
September 28, 2013, 08:54:16 PM
A few more minor changes happening to the UI related to how really large numbers can screw up the formatting on the dashboard.
If you have more than 10,000,000 accepted shares on a worker, it will now be divided by 1,000 and a 'k' appended. If you have more than 100,000 of a certain reject type, the same thing will happen. In order to make these numbers easier to parse, they now have commas added once these amounts are reached (example: 5,903k accepted).
If you have more than 10,000,000 accepted shares on a worker, it will now be divided by 1,000 and a 'k' appended. If you have more than 100,000 of a certain reject type, the same thing will happen. In order to make these numbers easier to parse, they now have commas added once these amounts are reached (example: 5,903k accepted).
September 28, 2013, 08:39:14 PM
Done. This was something I started on a while ago and never finished. All numbers on the site are now in GH/s. On the worker table, a worker under 1 GH/s will be measured in GH/s with 3 decimals (so you'll get MH/s rounded to the nearest MH).
That's awesome. Anyone still living in megahash ages shouldn't even be mining. So much easier on the eye. Thanks.
September 28, 2013, 03:09:33 PM
For your next assignment, figure out why the luck on several pools has gone down the crapper. heh, actually something doesn't feel right but i can't put my finger on it. It feels like the luck calculation is flawed in some way.
Similar to what I mentioned earlier talking with organofcorti: Bad luck is defined as a long period without blocks. That means at any given time, you're probably more likely to be experiencing bad luck rather than good luck. Good luck comes in very short bursts since they're defined as many blocks in a less than normal amount of time. Those bursts make up for that extended period of bad luck.
The other issue is network growth is outpacing most pools, so they're losing overall network share. BTC Guild actually lost a bit of network share recently now that MegaBigPower went solo. The smaller your share of the network, the worse bad luck feels since the time it takes to solve a block that takes 5-9x difficulty worth of shares is much longer when you're only 5-6% of the network.
So then the increase in overall hashrate without a proportional growth in a pool's hashrate would manifest as Bad Luck? That i can wrap my head around.
Not exactly, but the "time spent with bad luck" will increase. If a pool does not keep up with the network growth, they will (on average) have longer rounds. Similarly, if a pool would have a round that takes 7 times difficulty to complete, it will last even longer as their share of the network decreases between each difficulty. But the flip side is, the smaller your pool is compared to the network, the higher your potential luck can be in a given time frame, which is what offsets that bad luck. It's all a matter of variance.
September 28, 2013, 02:42:12 PM
For your next assignment, figure out why the luck on several pools has gone down the crapper. heh, actually something doesn't feel right but i can't put my finger on it. It feels like the luck calculation is flawed in some way.
Similar to what I mentioned earlier talking with organofcorti: Bad luck is defined as a long period without blocks. That means at any given time, you're probably more likely to be experiencing bad luck rather than good luck. Good luck comes in very short bursts since they're defined as many blocks in a less than normal amount of time. Those bursts make up for that extended period of bad luck.
The other issue is network growth is outpacing most pools, so they're losing overall network share. BTC Guild actually lost a bit of network share recently now that MegaBigPower went solo. The smaller your share of the network, the worse bad luck feels since the time it takes to solve a block that takes 5-9x difficulty worth of shares is much longer when you're only 5-6% of the network.
So then the increase in overall hashrate without a proportional growth in a pool's hashrate would manifest as Bad Luck? That i can wrap my head around.
September 28, 2013, 02:32:01 PM
For your next assignment, figure out why the luck on several pools has gone down the crapper. heh, actually something doesn't feel right but i can't put my finger on it. It feels like the luck calculation is flawed in some way.
Similar to what I mentioned earlier talking with organofcorti: Bad luck is defined as a long period without blocks. That means at any given time, you're probably more likely to be experiencing bad luck rather than good luck. Good luck comes in very short bursts since they're defined as many blocks in a less than normal amount of time. Those bursts make up for that extended period of bad luck.
The other issue is network growth is outpacing most pools, so they're losing overall network share. BTC Guild actually lost a bit of network share recently now that MegaBigPower went solo. The smaller your share of the network, the worse bad luck feels since the time it takes to solve a block that takes 5-9x difficulty worth of shares is much longer when you're only 5-6% of the network.
September 28, 2013, 02:21:22 PM
Is it time to change Mh/s to Gh/s on your tables?
Done. This was something I started on a while ago and never finished. All numbers on the site are now in MH/s. On the worker table, a worker under 1 GH/s will be measured in GH/s with 3 decimals (so you'll get MH/s rounded to the nearest MH).
Take a break man. heh did you mix up the Ms and Gs in this post?
Whoops. All numbers are in GH/s :p
For your next assignment, figure out why the luck on several pools has gone down the crapper. heh, actually something doesn't feel right but i can't put my finger on it. It feels like the luck calculation is flawed in some way.
September 28, 2013, 02:11:04 PM
Is it time to change Mh/s to Gh/s on your tables?
Done. This was something I started on a while ago and never finished. All numbers on the site are now in MH/s. On the worker table, a worker under 1 GH/s will be measured in GH/s with 3 decimals (so you'll get MH/s rounded to the nearest MH).
Take a break man. heh did you mix up the Ms and Gs in this post?
Whoops. All numbers are in GH/s :p
September 28, 2013, 02:09:12 PM
Is it time to change Mh/s to Gh/s on your tables?
Done. This was something I started on a while ago and never finished. All numbers on the site are now in MH/s. On the worker table, a worker under 1 GH/s will be measured in GH/s with 3 decimals (so you'll get MH/s rounded to the nearest MH).
Take a break man. heh did you mix up the Ms and Gs in this post?
September 28, 2013, 01:56:28 PM
Is it time to change Mh/s to Gh/s on your tables?
Done. This was something I started on a while ago and never finished. All numbers on the site are now in GH/s. On the worker table, a worker under 1 GH/s will be measured in GH/s with 3 decimals (so you'll get MH/s rounded to the nearest MH).
September 28, 2013, 01:31:26 PM
Is it time to change Mh/s to Gh/s on your tables?
September 28, 2013, 12:12:05 PM
X-axis is actually not scaled to blocks solved. Y-axis is the luck (% of payout vs expectation), X-axis is shift ID (roughly time since shifts are normally the same length).
Good stuff... Is the 100% line based on pool speed and difficulty, or pool speed and calculated global hash rate? 100% line means payouts/block solves were exactly what you'd expect given the number of shares. You'll never see exactly 100% for a single data point since currently each block is paid out to ~2.5 billion shares, which is not an exact multiple of difficulty. However, the average should always trend towards 100% by the end of a difficulty period. Only early in a difficulty will you see big swings.
Example: Current difficulty is 148,819,200. To be exactly at expectation, a shift would need 2,500,000,000 / 148,819,200 = 16.79 blocks. Since you can't find a fractional block, a "neutral" shift would either be 16 blocks (slightly under expectation) or 17 blocks (slightly above).
September 28, 2013, 12:08:20 PM
X-axis is actually not scaled to blocks solved. Y-axis is the luck (% of payout vs expectation), X-axis is shift ID (roughly time since shifts are normally the same length).
Good stuff... Is the 100% line based on pool speed and difficulty, or pool speed and calculated global hash rate? Jump to: