Skip to content

Timing history truncation/compaction #1

@jerluc

Description

@jerluc

Currently, whenever sw records timing statistics, it just keeps accumulating into the history.json file. While this provides the most accurate aggregate statistics, this also means that the history.json file size is unbounded and may eat away at disk space and degrade performance over time.

We should figure out how to either:

  1. Truncate timing histories such that only the last X timings are persisted, OR
  2. Figure out a way to compact the histories together in a way that leaves the aggregates relatively in tact (e.g. a moving average vs. mean)

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinggood first issueGood for newcomers

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions