Feature: build stats pruning functionality #4

Closed
opened 2014-09-26 22:07:13 +02:00 by Beanow · 1 comment
Beanow commented 2014-09-26 22:07:13 +02:00 (Migrated from github.com)

After running the maintenance jobs for ~2 months now, I have generated 6.2MB of statistical data about site-probe speeds and profile scrape speeds. These are never displayed as detailed as they are stored in the database. So I think the timespan for these high detail statistics should be limited and older results should be averaged to save space.

  • Add a threshold after which site-scrape will be a daily avg.
  • Add a threshold after which site-scrape will be dropped.
  • Add a threshold after which site-probe will be dropped.
After running the maintenance jobs for ~2 months now, I have generated 6.2MB of statistical data about site-probe speeds and profile scrape speeds. These are never displayed as detailed as they are stored in the database. So I think the timespan for these high detail statistics should be limited and older results should be averaged to save space. - Add a threshold after which site-scrape will be a daily avg. - Add a threshold after which site-scrape will be dropped. - Add a threshold after which site-probe will be dropped.
MrPetovan commented 2018-11-05 06:01:52 +01:00 (Migrated from github.com)

Detailed stats will be removed in the next version.

Detailed stats will be removed in the next version.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: friendica/dir#4
No description provided.