ActivityWatch / ActivityWatch/aw-watcher-input

Solving rendering delay in timeline

Aperta
#23 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Python
Stelle
169
Fork
37
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

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

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.