High CPU usage #237
Labels
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
Closed
|
I ran into the same situation on the Mac platform. After I extended the timeout, the situation disappeared. |
|
fixed by #262 as well |
This comment was marked as duplicate.
This comment was marked as duplicate.
arp242
added a commit
that referenced
this issue
Aug 1, 2022
The timeout for unix.Kevent() is causing issues; every 100ms it will do a new unix.Kevent() syscall, which isn't too efficient: even if you have just one change an hour, you will still keep calling kevent() ten times per second, resulting in a needlessly high CPU usage. Without a timeout, kevent() will block indefinitely until there are some events, which is much more efficient. We can't just remove the timout however, since we can't interrupt the kevent() call on FreeBSD and NetBSD, and it will hang forever. This issue is described in more detail here: #262 (comment) To solve this we register a new kevent() with the file descriptor set to the closepipe; when this pipe is closed an event is sent and kevent() will stop blocking. This is a rebased version of #124. Fixes #89 Fixes #237 Fixes #333 Supersedes and closes #124 Supersedes and closes #262 Supersedes and closes #334
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello all,
I have a file, monitored by fsnotify, in used from another process and I have a leak of CPU (attached pprof diagram). What do you think about it?
The text was updated successfully, but these errors were encountered: