You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 17, 2023. It is now read-only.
Have you confirmed that building the interval tree is the main contributor for startup time? If so, it's perhaps worth taking a look at whether a majority of the time is spent doing calls in Python or if more time is spent in the low-level C code that NCLS uses for the underlying interval tree implementation. If the latter constitutes a majority of the time spent, then it may be worth optimizing the low level code. Because the interval tree only needs to be built once and then can be used on multiple threads, perhaps a custom low-level implementation of an interval tree that allows it to be built cooperatively by multiple threads would speed up this process.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
can we add a prebuilt index for the human genome .gtf / .fa that would load much faster?
hg38.fa -> 3 Gb
hg38.gtf -> 144 Mb
The text was updated successfully, but these errors were encountered: