ActivityWatch / ActivityWatch/aw-watcher-input

Solving rendering delay in timeline

Open
#23 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
169
Forks
37
PR merge metrics
No merged PRs in 30d

Description

I compiled activity watch with watcher-input myself and everything works just fine, but after a whole day the timeline rendering takes ages. That's because of the rendering of all keypresses and mouseevents.
The activity tab loads instant and the aggregated data is shown instantly. On the timeline tab the "Events shown" are very fast too, only the bars indicating the activity take long for the watcher input bucket.

Which of these strategies would be the best?
- Exclude the watcher-input from the timeline visualisation
- Load the watcher-input data in larger chunks instead of every event for the timeline
- aggregate data and commit only every 5 seconds
- ...

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.