Enhancement request

Discussion of development releases of Prohashing / Requests for features
Forum rules
The Development forum is for discussion of development releases of Prohashing and for feedback on the site, requests for features, etc.

While we can't promise we will be able to implement every feature request, we will give them each due consideration and do our best with the resources and staffing we have available.

For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Locked
User avatar
rootdude
Posts: 76
Joined: Wed Jan 07, 2015 3:14 pm

Enhancement request

Post by rootdude » Thu Jul 02, 2015 3:28 pm

Hey Steve and Chris -

My request is simple - add a simple speedometer to the 'Earnings' UI that shows an 'anticipated' or 'expected' payout based on the payout rate since the last payout.

EX.

24 / (hours since last payout) * confirmed reward = anticipated payout

So as an example... say it's 12PM (12 hours after last payout) and your confirmed balance is, say, .25 BTC.

(24 / 12) * .25 = .50 BTC

As a small addition, there can be an up or down red or green arrow next to the anticipated payout that indicates whether for the last hour the payout rate is on an upswing or downswing.

Thoughts?

I do this math (mainly in my head) when I check in to have a look at how we are doing - it'd be nice just to glance at it and know how the day might end up...

Thanks,
rootdude
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: Enhancement request

Post by Steve Sokolowski » Fri Jul 03, 2015 9:14 am

This is a great suggestion. I can't promise that we'll be able to implement it soon, as there are many other issues ahead of it, but we will definitely look into it.

Before you get excited, though, I should warn that what you're suggesting may be too CPU-intensive, though. The problem here is that profitability constantly goes up and down by the second, so we can't just take instant profitability at any give time and compare it to instant profitability an hour later. Instead, we would have to scan through a large number of shares and take an average, like we do at the end of the day to compute how much was earned the previous day.

But it takes almost three minutes to compute the previous day's earnings, so we need to see if there is a more efficient way of performing these computations.
User avatar
Chris Sokolowski
Site Admin
Posts: 945
Joined: Wed Aug 27, 2014 12:47 pm
Location: State College, PA

Re: Enhancement request

Post by Chris Sokolowski » Fri Jul 03, 2015 4:57 pm

Perhaps you can do the extrapolation periodically, perhaps every 30 minutes, instead of at the moment a user loads a page. It may be less accurate, but it should be close enough to be useful.
User avatar
rootdude
Posts: 76
Joined: Wed Jan 07, 2015 3:14 pm

Re: Enhancement request

Post by rootdude » Fri Jul 03, 2015 5:57 pm

Steve Sokolowski wrote:...may be too CPU-intensive, though. The problem here is that profitability constantly goes up and down by the second, so we can't just take instant profitability at any give time and compare it to instant profitability an hour later.
The trending isn't as important as having the reference number to take a quick look at... so no need to go to great lengths. And, of course, wherever it fits in the grand scheme of things is up to you and Chris of course - it's just a suggestion and I'm perfectly capable of figuring this out on my own.

But, if/when you get ready to implement, and desire a way to keep the CPU cost of the trending down, I have a few ideas how to do that... you can just hit me up when this comes up on the list.

Thanks Guys,
rootdude
Locked