This repository has been archived by the owner on Aug 20, 2024. It is now read-only.
slow validation caused by string replaceAll to remove nulls #120
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.
Fixes #90
It turns out
replaceAll
to removenull
values from the json string representation of the samplesheet is the bottleneck here.Using
JsonGenerator
with.excludeNulls
to convert the object to a string and back again to aJSONArray
solves this.Using a single-end samplesheet with 60 rows:
before
after
N.B. Interestingly it should be noted that if you use a
yaml
input format samplesheet rather than acsv
you do not see the same issue. This leads me to suspect thatnull
values in ayaml
are being parsed differently at some point before this: