Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 443. (Read 4382714 times)
January 16, 2014, 10:56:26 PM
Not to rub it in, but mine just reconnected and my reward looks awesome with the smaller pool right now...
January 16, 2014, 10:29:20 PM
I've got a small and big miner and the smaller hasnt connected for 36 mins but the big one hasnt connected for 1hour, 12 mins.
January 16, 2014, 10:27:02 PM
Strangely my biggest worker got booted but my smaller ones are still mining
January 16, 2014, 10:23:45 PM
January 16, 2014, 10:18:25 PM
It's working fine for me but I noticed that the hashing is down by close to half. Great for the remaining miners IF we can turn over some blocks!
January 16, 2014, 10:16:15 PM
Is the pool currently down?
January 16, 2014, 08:28:45 PM
Why I like mining on slush
21478 2014-01-16 23:27:08 0:00:20 2784211 1680 0.01479891 280890 25.01347342 88 confirmations left
21477 2014-01-16 23:26:48 2:15:28 1344679965 471240 0.00814433 280889 25.05321188 87 confirmations left
Nearly got a double in reward from that block.
21478 2014-01-16 23:27:08 0:00:20 2784211 1680 0.01479891 280890 25.01347342 88 confirmations left
21477 2014-01-16 23:26:48 2:15:28 1344679965 471240 0.00814433 280889 25.05321188 87 confirmations left
Nearly got a double in reward from that block.
If you don't mind my asking, what's your hashrate on slush, around 210GH/s?
You are close but it is 240 GH/s
January 16, 2014, 08:19:32 PM
Why I like mining on slush
21478 2014-01-16 23:27:08 0:00:20 2784211 1680 0.01479891 280890 25.01347342 88 confirmations left
21477 2014-01-16 23:26:48 2:15:28 1344679965 471240 0.00814433 280889 25.05321188 87 confirmations left
Nearly got a double in reward from that block.
21478 2014-01-16 23:27:08 0:00:20 2784211 1680 0.01479891 280890 25.01347342 88 confirmations left
21477 2014-01-16 23:26:48 2:15:28 1344679965 471240 0.00814433 280889 25.05321188 87 confirmations left
Nearly got a double in reward from that block.
If you don't mind my asking, what's your hashrate on slush, around 210GH/s?
January 16, 2014, 08:00:24 PM
Why I like mining on slush
21478 2014-01-16 23:27:08 0:00:20 2784211 1680 0.01479891 280890 25.01347342 88 confirmations left
21477 2014-01-16 23:26:48 2:15:28 1344679965 471240 0.00814433 280889 25.05321188 87 confirmations left
Nearly got a double in reward from that block.
21478 2014-01-16 23:27:08 0:00:20 2784211 1680 0.01479891 280890 25.01347342 88 confirmations left
21477 2014-01-16 23:26:48 2:15:28 1344679965 471240 0.00814433 280889 25.05321188 87 confirmations left
Nearly got a double in reward from that block.
January 16, 2014, 11:23:42 AM
“Mr Bond, they have a saying in Chicago: 'Once is happenstance. Twice is coincidence. The third time it's enemy action'.”
Well, GHash.IO has done it to us again with block 280616. The timings are really weird: the timestamp for 280616 - 12:20:06 - is more than two minutes later than the received time - 12:17:31 (which is the same as the time claimed by Slush) - and is even nearly two minutes later than the next block, 280617, which was also bagged by GHash.IO. Something doesn't look right.Does anybody know if they have done this to other pools?
Though to be fair, we did solve two blocks in a row yesterday (280561 and 280562) and orphaned someone else's block (280562) when the network picked ours.
January 16, 2014, 11:07:09 AM
“Mr Bond, they have a saying in Chicago: 'Once is happenstance. Twice is coincidence. The third time it's enemy action'.”
Well, GHash.IO has done it to us again with block 280616. The timings are really weird: the timestamp for 280616 - 12:20:06 - is more than two minutes later than the received time - 12:17:31 (which is the same as the time claimed by Slush) - and is even nearly two minutes later than the next block, 280617, which was also bagged by GHash.IO. Something doesn't look right.Does anybody know if they have done this to other pools?
January 15, 2014, 03:20:51 PM
The pool automatically recognizes strength of your mining hardware and adjusts work difficulty for the miner accordingly. With Vardiff implemented, each miner is led to send results of its work to the server around 20 times per minute. That's the goal. If the miner is too fast, Vardiff increases the difficulty for its work and when too slow, the difficulty decreases.
This does not affect your score or rewards. For example: When your miner submits a proof of work with difficulty set to 5, it is counted as 5 shares by the pool. When submitted with difficulty 1 then only 1 share is counted. It takes 5x more work to find a proof of work when difficulty is set to 5 then when set to 1. So it is valued 5x more.
The algorithm re-evaluates your miner's strength continuously but it doesn't change the difficulty when your hashrate is stable.
This does not affect your score or rewards. For example: When your miner submits a proof of work with difficulty set to 5, it is counted as 5 shares by the pool. When submitted with difficulty 1 then only 1 share is counted. It takes 5x more work to find a proof of work when difficulty is set to 5 then when set to 1. So it is valued 5x more.
The algorithm re-evaluates your miner's strength continuously but it doesn't change the difficulty when your hashrate is stable.
January 15, 2014, 02:33:39 PM
Thanks for the info
January 15, 2014, 01:20:08 PM
Is this normal to see a 5ghs difference between miner stats and pool stats? Any info would be greatly appreciated.
Yes, because your miner has the exact info for your hardware capabilities, while the pool is trying to guess it with backward calculation based on the shares submitted from you. If you miner has a luck to find more - the pool will show more and the opposite. January 15, 2014, 12:43:53 PM
I feel such a Troll in this moment for have done that. Is always funny when they use those "big words" that briefly resumes everything.
Anyway, not a point of discussion for this thread.
Anyway, not a point of discussion for this thread.
January 15, 2014, 12:26:30 PM
EDIT. And if your can explain in 500 words what VARDIFF is, without looking in wikipedia or even google earth, I will tranfer you 1 Satoshi. Fees on my own.
PD. "fluid" is not a substantive that you want to use for hashrate.| And... sorry, you were trying to answer only about "determining the hash rate the pool recognizes"
What about the other one hundred questions?Don't need 500 words to explain VARDIFF. Stands for Variable Difficulty which means that the higher your hash rate, the more work the pool sends to your miner (worker). Once you solve the work, all shares are sent at once then counted as a difficulty of one. It reduces the amount of traffic you need to send to the server. It's unrelated to the current difficulty of the network, only related to the difficulty the pool sets to your miner.
Keep your Satoshi.
January 15, 2014, 12:13:33 PM
EDIT. And if your can explain in 500 words what VARDIFF is, without looking in wikipedia or even google earth, I will tranfer you 1 Satoshi. Fees on my own.
PD. "fluid" is not a substantive that you want to use for hashrate.| And... sorry, you were trying to answer only about "determining the hash rate the pool recognizes"
What about the other one hundred questions?Don't need 500 words to explain VARDIFF. Stands for Variable Difficulty which means that the higher your hash rate, the more work the pool sends to your miner (worker). Once you solve the work, all shares are sent at once then counted as a difficulty of one. It reduces the amount of traffic you need to send to the server. It's unrelated to the current difficulty of the network, only related to the difficulty the pool sets to your miner.
Fluid - as in the Internet is a fluid network with sometimes it losing packets, capacity issues, network connectivity issues. If your miner solves 1,000 difficulty 1 equivalent shares, but then goes to send them to the pool and there's a network issue, you could lose them. Or if a new block is found or the server sends new work, the work you did on those shares is discarded. All of that will be reflected in how the pool determines the hash rate. Yes, therefore the hash rate is fluid.
Keep your Satoshi.
January 15, 2014, 03:37:20 AM
working on more difficult work
There is no more (or less) difficult work - you always work on the same block (and data) as the rest of the world.VARDIFF is the minimum result (share diff) you report back to the pool in order to send on average ~15 reports per minute.
If your hardware is capable of calculating 1000 jobs per minute (~72GH/s) and each job returns at least one 'diff 1 share' (which is exactly the case with dblSHA256) - you will need to send 1000 reports, which is too much load for the server and your bandwidth
But because 500 from those will have diff of 2 or more, 250 will have diff of 3 or more etc. ... then for you to send ~15 reports means that you need to send back only those shares that are of diff 7 or higher
January 14, 2014, 07:42:19 PM
My understanding of VARDIFF is that the pool sends different levels of difficulty to you based on your miners capability. i.e. 125/22. This gives you better awards for working on more difficult work without the need to hog a lot of I/o bandwidth. I believe it helps keep the traffic in and out of the server to a more predictable level while still giving stronger miners more work, therefor more rewards.
Again this is just my interpretation ?
Again this is just my interpretation ?
January 14, 2014, 07:14:38 PM
Hi ya all,
It is not a complain, but I have been noticing last months, that every time that pool's hashrate has a huge hop (like >20TH/s) we are experiencing problems of "stolen" blocks or long rounds (>6h). The last 48h is another example. Hope this new hardware Slush implemented is going to kill this glitches with time.
Salute all Slusher's.
It is not a complain, but I have been noticing last months, that every time that pool's hashrate has a huge hop (like >20TH/s) we are experiencing problems of "stolen" blocks or long rounds (>6h). The last 48h is another example. Hope this new hardware Slush implemented is going to kill this glitches with time.
Salute all Slusher's.
It's not a hardware issue on Slush's end. During long rounds, many people will hop to other pools. You'll see a drop in hashing power which means that there's less chance to find a block compounding the problem. Also, the hash rate is fluid meaning it can vary even if no miners came or went. Hardware errors, vardiff, etc. play a factor in determining the hash rate the pool recognizes.
Sorry, but, answering to your assumption about "factors". I am a systems engineer certified in a lot of technologies (and updated my certs) and what your are talking and assuming is "Coincidence". Which with time and experience your know that coincidence does not exist anymore talking about computering. It is like talking about "magic, or how the small men inside the server trick you", and yes sure you can "fix up a server hitting it enough times with your hand".
People, please. Think.
EDIT. And if your can explain in 500 words what VARDIFF is, without looking in wikipedia or even google earth, I will tranfer you 1 Satoshi. Fees on my own.
PD. "fluid" is not a substantive that you want to use for hashrate.| And... sorry, you were trying to answer only about "determining the hash rate the pool recognizes"
What about the other one hundred questions? Jump to: