ActivityWatch / ActivityWatch/aw-watcher-input

Solving rendering delay in timeline

未關閉
#23 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
Python
星號
169
分支
37
PR 合併指標
30 天內沒有已合併 PR

描述

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

貢獻指南

這個儲存庫沒有索引到貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。