ActivityWatch / ActivityWatch/aw-watcher-input

Solving rendering delay in timeline

Ouverte
#23 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Python
Étoiles
169
Forks
37
Métriques de merge des PR
Aucune PR mergée en 30 j

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
- ...

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.