New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance improvements #98

Closed
ErikBjare opened this Issue Aug 24, 2017 · 3 comments

Comments

Projects
None yet
1 participant
@ErikBjare
Copy link
Member

ErikBjare commented Aug 24, 2017

aw-server is taking too much CPU for my taste while running aw-watcher-afk and aw-watcher-window (~10% in htop isn't unusual, I've seen worse sometimes) and I think its time we did a little optimization.

The heartbeat API is the primary target for most optimizations since it's the most called endpoint.

Alternatives:


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@ErikBjare

This comment has been minimized.

Copy link
Member

ErikBjare commented Nov 5, 2017

Should probably mention that heartbeats with non-zero duration are supported since ActivityWatch/aw-core#47 (not tested, however)

Should make it easy to pre-merge heartbeats clientside.

@ErikBjare

This comment has been minimized.

Copy link
Member

ErikBjare commented Jan 4, 2018

@johan-bjareholt has started working on client-side merging of events in ActivityWatch/aw-client#25

@ErikBjare ErikBjare removed this from the v0.8 milestone Feb 13, 2018

@ErikBjare

This comment has been minimized.

Copy link
Member

ErikBjare commented May 29, 2018

I think we've gotten enough performance improvements for now with ActivityWatch/aw-server#32 and ActivityWatch/aw-client#33. Closing.

@ErikBjare ErikBjare closed this May 29, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment