-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
% growth over last period #323
Comments
confirm with @farski this is still part of the design |
That column was included in an early mockup more as a placeholder, since it was before what we knew we could get out of Castle in a performant way. I don't think we ever got to a point where it was spec'd as a requirement for v1. The new table designs allow for additional columns, so if there are any other, useful metrics we can add without sacrificing speed I'm all for that, but I'm not married to this particular stat in any way. |
It's just another request to Castle of the same kind and breadth we're already making. |
Got it. I haven't benchmarked the API recently, but I know there were some tickets about making performance improvements, so I'll have to defer to someone else how much sense it makes to make another request. I've still been getting some 20-30s/timeout requests as things are right now, but I'm not sure if the performance refactoring has happened or not. Maybe @cavis could weigh in? |
Haven't looked into the performance woes yet. Probably a requirement for something like this (which will just double the slowness for those pages). |
In desktop view, user agent and geo data should have a column of % growth up or down from the last period for the geo region/agent/os/form factor.
The text was updated successfully, but these errors were encountered: