Out of curiosity what new features are you planning on to add?
* New features will be activated within a few days
Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 990. (Read 4382653 times)
July 20, 2011, 02:48:13 PM
July 20, 2011, 10:23:33 AM
Slush, is there a way to clear data from my graphs? My production has dropped quite a bit from when I was producing 5-7 BTC/day, and the current variation is very difficult to see. Essentially, the graph is now useless to me, and the stats are much more meaningful.
Thanks.
+1Thanks.
or something to choose range in days
July 20, 2011, 09:21:16 AM
Slush, is there a way to clear data from my graphs? My production has dropped quite a bit from when I was producing 5-7 BTC/day, and the current variation is very difficult to see. Essentially, the graph is now useless to me, and the stats are much more meaningful.
Thanks.
Thanks.
July 20, 2011, 07:12:17 AM
Ok well it showed up. But in our recent 140 minute block I mined for the first 120 minutes before my PC crashed, during which I submitted about 1300 shares. My reward per block is normally 0.015 BTC but this blockI was only rewarded 0.0012 (10x less)?? Why isn't my work being counted?
Because of the score based system. Each share is worth more than the previous one, on an exponential curve.
That's ridiculous, I legitimately submitted shares in 120/140 minutes because of a BSOD and I get 10 times less?
I may as well just not have mined for 2 hours at all...all of the money that I worked for is getting paid to everyone else who didn't legitimately work for it...
That's the reason I switched to deepbit. I like slush but my computer network is not always stable.
To be fair, slush implemented the score based system to prevent pool hopping (which is bad to the pool). I just wish they implement a different method such as delayed stats.
BTC Guild just implemented delayed stats within the past week. The jury is still out on whether things have improved for those of us who don't pool hop, but time will tell.
Delayed stats sounds very good. Lets face it, theres always *something* going on. Even if its on a small scale, some minor tweak or what, how many of you said "never touch a running system" or "i wont ruin my afternoon" because of the score system ?
I dont care how many rounds, shares and so on. Reading that stuff a day later would be totally ok.
All i need to know is, if its running ok and if performance is ok, lag maybe, whatever.
Realtime details are not necessary. Just give us a basic idea and everything is fine.
July 19, 2011, 05:51:27 PM
Slush, I'm glad to see you still up and running, and you've doubled your thread's posts since the last time I was here. Just checking in to say thanks for your service, and I'm proud to once again add my 380Mhash to your pool. (wow, that was a lot, not too long ago.)
July 19, 2011, 06:05:02 AM
Thanks slush! My room is warm once again!
July 19, 2011, 05:57:28 AM
Yes, one backend had issue (~20 minutes) in time when I wasn't online. It's already fixed, I'm sorry for troubles.
July 19, 2011, 05:39:38 AM
MSG1: Call to bitcoind failed: [Errno socket error] [Errno 111] Connection refused
MSG2: Backend is not connected!
Looks like the backend crashed about 20-30 mins ago.
EDIT: Looks like its back up again!
MSG2: Backend is not connected!
Looks like the backend crashed about 20-30 mins ago.
EDIT: Looks like its back up again!
July 19, 2011, 05:38:00 AM
July 18, 2011, 11:35:35 AM
Hi Slush,
After watching my worker stats for the past few days with my Cacti template that uses the JSON API, I noticed the last share times seemed to jump around for the running workers.
The following graph shows another worker that was shut down late Thursday night and stopped submitting shares. The initial jump to ~9600 seconds at ~22:40 (the time I shut the worker down) is odd given the previous values, but the growth rate from then to the end of the graph on the right looks normal.
Since the JSON API provides the last_share time in UNIX time format, my script simply subtracts the last_time value for the worker from the current time to get the elapsed time in seconds. It seems to work most of the time, save the weird spikes shown in the first graph.
Is it possible one or more of the servers providing the last share data aren't synced time-wise resulting in these jumps as load balancing shifts the JSON API query to one of the affected servers?
After watching my worker stats for the past few days with my Cacti template that uses the JSON API, I noticed the last share times seemed to jump around for the running workers.
The following graph shows another worker that was shut down late Thursday night and stopped submitting shares. The initial jump to ~9600 seconds at ~22:40 (the time I shut the worker down) is odd given the previous values, but the growth rate from then to the end of the graph on the right looks normal.
Since the JSON API provides the last_share time in UNIX time format, my script simply subtracts the last_time value for the worker from the current time to get the elapsed time in seconds. It seems to work most of the time, save the weird spikes shown in the first graph.
Is it possible one or more of the servers providing the last share data aren't synced time-wise resulting in these jumps as load balancing shifts the JSON API query to one of the affected servers?
Still no response on this eh? Just for reference, this is what it looks like when the time is reported correctly (from BTC Guild):
July 18, 2011, 11:16:44 AM
I have decided, I like this pool the best. The greasemonkey script is a major +. GUIMiner shows 322 Mhash/s & bitcoin.cz shows nearly identical rate, plus all the other features is really cool.
Cannot wait for 6-8 more months to get moar gear to mine. Addicting & Fantastic!
Cannot wait for 6-8 more months to get moar gear to mine. Addicting & Fantastic!
July 18, 2011, 11:05:34 AM
Ok well it showed up. But in our recent 140 minute block I mined for the first 120 minutes before my PC crashed, during which I submitted about 1300 shares. My reward per block is normally 0.015 BTC but this blockI was only rewarded 0.0012 (10x less)?? Why isn't my work being counted?
Because of the score based system. Each share is worth more than the previous one, on an exponential curve.
That's ridiculous, I legitimately submitted shares in 120/140 minutes because of a BSOD and I get 10 times less?
I may as well just not have mined for 2 hours at all...all of the money that I worked for is getting paid to everyone else who didn't legitimately work for it...
That's the reason I switched to deepbit. I like slush but my computer network is not always stable.
To be fair, slush implemented the score based system to prevent pool hopping (which is bad to the pool). I just wish they implement a different method such as delayed stats.
BTC Guild just implemented delayed stats within the past week. The jury is still out on whether things have improved for those of us who don't pool hop, but time will tell.
July 17, 2011, 11:14:22 PM
Ok well it showed up. But in our recent 140 minute block I mined for the first 120 minutes before my PC crashed, during which I submitted about 1300 shares. My reward per block is normally 0.015 BTC but this blockI was only rewarded 0.0012 (10x less)?? Why isn't my work being counted?
Because of the score based system. Each share is worth more than the previous one, on an exponential curve.
That's ridiculous, I legitimately submitted shares in 120/140 minutes because of a BSOD and I get 10 times less?
I may as well just not have mined for 2 hours at all...all of the money that I worked for is getting paid to everyone else who didn't legitimately work for it...
That's the reason I switched to deepbit. I like slush but my computer network is not always stable.
To be fair, slush implemented the score based system to prevent pool hopping (which is bad to the pool). I just wish they implement a different method such as delayed stats.
July 17, 2011, 01:28:39 AM
fricking waaa
July 16, 2011, 07:24:29 PM
Ok well it showed up. But in our recent 140 minute block I mined for the first 120 minutes before my PC crashed, during which I submitted about 1300 shares. My reward per block is normally 0.015 BTC but this blockI was only rewarded 0.0012 (10x less)?? Why isn't my work being counted?
Because of the score based system. Each share is worth more than the previous one, on an exponential curve.
That's ridiculous, I legitimately submitted shares in 120/140 minutes because of a BSOD and I get 10 times less?
I may as well just not have mined for 2 hours at all...all of the money that I worked for is getting paid to everyone else who didn't legitimately work for it...
July 16, 2011, 06:42:55 PM
Ok well it showed up. But in our recent 140 minute block I mined for the first 120 minutes before my PC crashed, during which I submitted about 1300 shares. My reward per block is normally 0.015 BTC but this blockI was only rewarded 0.0012 (10x less)?? Why isn't my work being counted?
Because of the score based system. Each share is worth more than the previous one, on an exponential curve.
July 16, 2011, 04:53:12 PM
Ok well it showed up. But in our recent 140 minute block I mined for the first 120 minutes before my PC crashed, during which I submitted about 1300 shares. My reward per block is normally 0.015 BTC but this blockI was only rewarded 0.0012 (10x less)?? Why isn't my work being counted?
July 15, 2011, 05:13:16 PM
July 15, 2011, 04:30:36 PM
I just submitted 250 shares in a round and my reward is none???
Processing of shares can take some time, so it is pretty normal that you see 'none' for freshly mined blocks. So - yes - check again.
July 15, 2011, 03:39:28 PM
I just submitted 250 shares in a round and my reward is none???
Check again
Jump to: