Async CatTree and dir parser #186
Merged
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
…dexes and disk sub-index config
ate47
force-pushed
the
dev_async_cattree
branch
from
f8e4b16 to
8335366
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.
This PR add 2 async versions for the DirParser and the CatTree
The CatTree async version can be selected with the
loader.cattree.async=[boolean]option, knowing a cat is most likely faster than the time before the next cat, you can't select more than 2 threads.The DirParser async version can be selected with the
parser.dir.async=[number]option, 1 = sync, 0 = processor count, n = using n threads.I've also added a commit to use large arrays in Bitmap375Disk to use larger indexes.
EDIT:
For example, when loading 200 different NT files (same size), it take 4 times less time to load them with the dir parser: