Add options --ulimit
und --parser-buffer-size
configurable for qlever index
command
#132
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.
So far, the
ulimit
was set to1048576
when the size of the input files is larger than10 GB
, which is a simplisitic and rough heuristic. In particular, this does not work when the RDF data is produced from the input file and the latter is relatively small compared to the former. Or when the OS allows increasing theulimit
but not that much. Now theulimit
can also be set explicitly via the option--ulimit
of theqlever index
command, or via the variableULIMIT
in the[index]
section of the Qleverfile.Further, ad-freiburg/qlever#1698 introduced an option
--parser-buffer-size
toIndexBuilderMain
, see there for the effect. This can now also be set explicitly via the option--parser-buffer-size
of theqlever index
command, or via the variablePARSER_BUFFER_SIZE
in the[index]
Qleverfile.