Delay after saving about atom-wakatime

[alanhamlett]

This is on Windows, Mac, or Linux?

The two places which could cause slowness are:

1. finding the current project by looping over all projects
2. executing wakatime-cli in a background python process

How many project folders do you have open in Atom?

Executing wakatime-cli happens async, but maybe Atom somehow blocks other onDidSave events from executing.

[daveyjones]

I'm on a MacBook Pro running OS X 10.11.3. I only have 4 projects, so it's probably not 1. It seems like a conflict with onDidSave is more likely. The LESS compiler I'm using is less-autocompile. I haven't quite figured out exactly how to re-produce. I'm able to resolve the issue temporarily by resetting the wakatime plugin, but after a time the delay returns. I'll try to figure out the exact path to reproduce.

[daveyjones]

I think this may be related to #31. After each save, the CPU usage for Atom Helper is quite high (see screenshot). I wonder if Atom is waiting for this process to finish before executing other onDidSave events due to the high CPU usage. (I'm not sure if Atom is that smart.)

[alanhamlett]

I can try using BufferedProcess instead of child_process.execFile but the former is just a wrapper of the latter using spawn instead of execFile so I'm not sure it would make any difference.

With wakatime installed but less-autocompile plugin uninstalled, does Atom Helper still use such high CPU?

I'm not able to reproduce it with less-autocompile installed, but my LESS files don't have the custom out, sourcemap, ... parameters on the first line of the LESS file.

[daveyjones]

I'm actually going to close this issue. I don't think it's related to WakaTime at all. I've read that others are having issues with Atom Helper and high CPU usage. One suggestion I found was to disable the built-in spell-check package. This seems to have solved it for me.

[alanhamlett]

Oh that's a relief, I was stuck on this one. 😌