With kqueue, we don't need to constantly check the snippet #2016
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Constantly going to the start of the logfile, checking the snippet, going back to where we were and then reading is a massive drain on the filesystem for zero benefit with kqueue.
allinurl
force-pushed
the
master
branch
2 times, most recently
from
0550432
to
b1332f5
Compare
allinurl
force-pushed
the
master
branch
5 times, most recently
from
3d5333b
to
6c68a6e
Compare
allinurl
force-pushed
the
master
branch
7 times, most recently
from
31e2ac1
to
c6199f6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Constantly going to the start of the logfile, checking the snippet,
going back to where we were and then reading is a massive drain
on the filesystem for zero benefit with kqueue.