avoid isfile calls on find as much as possible #676
Merged
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.
In
find, ifwalkalso includes thepathif it's a file, it should already be included in theout.So, if
outis not empty, we can safely assume that it is either a directory or a file. So, we don't needto make an extra
isfilecall.Though, if the path was an empty directory or if the walk does not return the file, we'll still be making an
isfilecall, which is unfortunate but better than before, where we were making an additional call for each find.This was noticed in DVC when trying to migrate to WebdavFS, which was making remote cache querying noticeably slower when traversing through the caches.
Please let me know if I'm missing something here, or anything else that needs to be considered here. :)