You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
_get_and_store_range on the server already stores pipeline_range to the user profile, which has start_ts and end_ts.
We can extend _get_and_store_range to also store total_trips and labeled_trips.
For last_call, we can look at stats/server_api_time and look at the last GET and last PUT calls
start by moving the _get_and_store_range to a real pipeline stage with its own timer. We can deploy that right now (today). Then when the real changes are done we can see the tradeoff in increased time on the server with decreased time on the admin dashboard.
Optimizing admin dashboard
add_user_stats
op-admin-dashboard/utils/db_utils.py
Line 433 in 5e1b235
_get_and_store_range
on the server already storespipeline_range
to the user profile, which hasstart_ts
andend_ts
.We can extend
_get_and_store_range
to also storetotal_trips
andlabeled_trips
.For
last_call
, we can look atstats/server_api_time
and look at the last GET and last PUT calls@TeachMeTW
The text was updated successfully, but these errors were encountered: