[ANN][Pool][Profit-Switch][Optional Auto-Exchange per Coin][Vardiff] ~ Hashcows

[nearmiss]

I've got what I think is a simple suggestion for the stats page.  Next to "My Est. Earnings" add a column for "this rate over 24hrs" or something along those lines where the time that round took is divided into the amount of time in a 24 hr period and multiplied by the Estimated Earnings column.  This gives a normalized view of each round that is easy to compare against previous rounds and other coins.  (Plus it will save me from having to do that on my side when a round completes )

Example:

Code:

Round #	Coin	Length		M.B.	M.C.	I.B.	I.C.	C.P.O.	C.A.T.	My Est. Earnings 24hrs@rate
693	GLD	00:25:16	0	0	53	2385.6	0	0	0.000265 BTC	.01510 BTC
691	GDC	00:09:37	1	1000	25	25000	39.44	960.56	0.000036 BTC	.00539 BTC
690	CGB	00:09:53	0	0	4	10	0	0	0.000071 BTC	.01034 BTC
687	WDC	00:40:14	59	3702.07	0	0	96.15	3605.92	0.00035 BTC	.01252 BTC

easy to see how each of those rounds compare even though they are different intervals of time - also, if you are storing what the Profitability number and difficulty were at the start of each round, this can give you additional data into what those numbers translate into for further tweaking of your handicap system.

I like this idea, though I'm a little concerned throwing it into the stats table may just confuse people a bit.  I'm picturing perhaps a tab with historical coin stats, where you can see stuff like 'average BTC return per last 24hrs' on a per coin basis (it could be a per round figure over 24hrs, or a weighted per unit of time figure over the last 24hrs, or whatever makes sense, maybe both!).   Not saying I can have something up by tomorrow (the list is ever growing!), but thoughts?

[rpg]

Guys, congrats for the excellent layout, but my stale rate is above the accepted rate. The ping is excellent at 21, so not sure whats causing it. Any ideas?

EDIT: stale rate vastly improved with Q=0

[aTriz]

*Update*

As requested, users now have a new tab on the Stats page "Worker Stats" to see individual worker information!

[rpg]

*Update*

As requested, users now have a new tab on the Stats page "Worker Stats" to see individual worker information!

let me know when you raise the difficulty, because with a stale rate of 10% is a waste electricity

[nearmiss]

*Update*

As requested, users now have a new tab on the Stats page "Worker Stats" to see individual worker information!

let me know when you raise the difficulty, because with a stale rate of 10% is a waste electricity

I've made some adjustments to starting difficulty (just a 16->32 jump for now), as well as how quickly vardiff will retarget you, and the maximum size it will bump/drop you.  This should let people get to their 'target difficulty' more quickly.  Hopefully this will have a positive affect on stales.  I didn't want to get too aggressive with it, but I can continue to adjust further as I get more feedback and monitor the results of these changes.

[rpg]

*Update*

As requested, users now have a new tab on the Stats page "Worker Stats" to see individual worker information!

let me know when you raise the difficulty, because with a stale rate of 10% is a waste electricity

I've made some adjustments to starting difficulty (just a 16->32 jump for now), as well as how quickly vardiff will retarget you, and the maximum size it will bump/drop you.  This should let people get to their 'target difficulty' more quickly.  Hopefully this will have a positive affect on stales.  I didn't want to get too aggressive with it, but I can continue to adjust further as I get more feedback and monitor the results of these changes.

great thanx, giving it a try now, will let you know

[powpow]

Is there an API to grab private user stats?

[rpg]

*Update*

As requested, users now have a new tab on the Stats page "Worker Stats" to see individual worker information!

let me know when you raise the difficulty, because with a stale rate of 10% is a waste electricity

I've made some adjustments to starting difficulty (just a 16->32 jump for now), as well as how quickly vardiff will retarget you, and the maximum size it will bump/drop you.  This should let people get to their 'target difficulty' more quickly.  Hopefully this will have a positive affect on stales.  I didn't want to get too aggressive with it, but I can continue to adjust further as I get more feedback and monitor the results of these changes.

it improved to around 7% still way too high Also something else is wrong. I'm supplying .73% of the network hash so  I would expect to see .73% of accepted shares, or close to it, but my shares are only .4% of the accepted shares. What's causing it?

[dolby]

hi

I can not register on your pool (every time i get Password must be between 6 - 20 characters.)

why?

[TheQuin]

hi

I can not register on your pool (every time i get Password must be between 6 - 20 characters.)

why?

It might be that numbers don't count as characters.

[dolby]

thx

[swiftshoot]

Something missing that should be displayed:

- Per Coin Profitability Rates.

This way we can see how it is really profitable.

Additionally, use the past data (accepts/rejects/round) to adjust profitability for the coin.

[johndec]

Guys, I love the concept of the pool and the ability to easily cash out into BTC but I'm bailing out until you sort out the problem with stales.  I've been mining for about 4 months now so I've got everything pretty finely tuned.  I've never had a stale problem with any other pool but this pool consistently shows my stales at about twice the pool average.  Maybe your stale reporting algorithm is flawed or your pool doesn't like my mining rig (If so, you guys are the only ones)..

To give you an example, I watched round 754, a CGB round, like a hawk.  Your stats consistently showed my miners running at 9 to 10% stales.  I've just spent the last hour mining CGB on another pool and my stale rate is below 2%.  And don't get me started about shit coins!    30-40% stales on your pool.

FYI, I'm using the latest version of guiminer scrypt and I've tried various flags and intensity adjustments but it hasn't made any difference.

[Eastwind]

*Update*

As requested, users now have a new tab on the Stats page "Worker Stats" to see individual worker information!

let me know when you raise the difficulty, because with a stale rate of 10% is a waste electricity

I've made some adjustments to starting difficulty (just a 16->32 jump for now), as well as how quickly vardiff will retarget you, and the maximum size it will bump/drop you.  This should let people get to their 'target difficulty' more quickly.  Hopefully this will have a positive affect on stales.  I didn't want to get too aggressive with it, but I can continue to adjust further as I get more feedback and monitor the results of these changes.

Do you reduce the difficulty when we mine the faster coins? I have a lot of stale on WDC in a rig with 4 X 7950 with intensity of 19.

[MrJay]

Guys, I love the concept of the pool and the ability to easily cash out into BTC but I'm bailing out until you sort out the problem with stales.  I've been mining for about 4 months now so I've got everything pretty finely tuned.  I've never had a stale problem with any other pool but this pool consistently shows my stales at about twice the pool average.  Maybe your stale reporting algorithm is flawed or your pool doesn't like my mining rig (If so, you guys are the only ones)..

To give you an example, I watched round 754, a CGB round, like a hawk.  Your stats consistently showed my miners running at 9 to 10% stales.  I've just spent the last hour mining CGB on another pool and my stale rate is below 2%.  And don't get me started about shit coins!    30-40% stales on your pool.

FYI, I'm using the latest version of guiminer scrypt and I've tried various flags and intensity adjustments but it hasn't made any difference.

Try using cgminer with these settings in your config/batch file:

--expiry 5 --queue 0 --scan-time 5

I'm testing various different settings on my rigs and the above with an intensity of 18 produces the best results for multi coin pools, for myself setting a higher intensity than 18 gives a higher amount of rejects.  A few people have mentioned that modifying such settings on stratum servers has no effect, but I really do find that there is a difference and I get a much lower reject rate.  Also if my miner detects a stale share and submits it, 90% of the time it is accepted:

[2013-09-19 10:35:21] Pool 0 stale share detected, submitting as user requested
[2013-09-19 10:35:21] Pool 0 stale share detected, submitting as user requested
[2013-09-19 10:35:21] Accepted ec29fc03 Diff 66/64 GPU 0 pool 0
[2013-09-19 10:35:21] Accepted fc2d41d8 Diff 122/64 GPU 0 pool 0

I'm also using a slightly older version of cgminer (2.11.4) as I found using some of the more up to date version my cards were running hotter, may just be myself or setup but for the past 3-4 months and plenty of playing around, this has been performing best.  If I mine LTC only with none of the above settings I get 1-2% rejected so I really think that the various different pools and coins take a bit of tweaking.  What might be good on one is not necessarily on another.

[Hydroponica]

Everyone on the pool, is getting the same stale rate, for the most part, so it won't effect your profits

[garumaru]

*Update*

As requested, users now have a new tab on the Stats page "Worker Stats" to see individual worker information!

Thank you!
If you can please get the notification for inactive workers working.

[DannyDisco]

Any plans to add LTC?

The only coins I'd like to keep are DGC, LTC, CGB and FST.

[TheQuin]

Any plans to add LTC?

The only coins I'd like to keep are DGC, LTC, CGB and FST.

Back on page 4 https://bitcointalk.org/index.php?topic=293872.msg3166550#msg3166550

[Turok]

hi, any idea how to lower the % of rejects? thanks