Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maximum Sequence Limit? #1261

Closed
ryhisner opened this issue Sep 23, 2023 · 2 comments
Closed

Maximum Sequence Limit? #1261

ryhisner opened this issue Sep 23, 2023 · 2 comments
Labels
t:ask Type: question, request of information 1

Comments

@ryhisner
Copy link

What is the maximum number of sequences Nextclade can run without crashing? Anything larger than about 2200 sequences usually crashes for me. Is there any way to increase the number of sequences it can accommodate, or is there a pretty hard limit? I've found that clicking off of the Nextclade tab makes it less likely to crash and that browsing the genomes while they upload almost guarantees a crash. I'm not sure why either of these things would have this effect though. Thanks.

@ryhisner ryhisner added good first issue Good for newcomers help wanted Extra attention is needed needs triage Mark for review and label assignment t:bug Type: bug, error, something isn't working labels Sep 23, 2023
@ivan-aksamentov
Copy link
Member

ivan-aksamentov commented Sep 23, 2023

There is no hard limit, but Nextclade Web is running all computations on your local computer and uses 32-bit WebAssembly underneath, which is limited to ~3.5 GBytes of memory (RAM). 64-bit WebAssembly exists, but is not yet supported in any browsers yet, so it is not currently feasible to use it.

Another soft limit is that Auspice cannot render this many nodes on the tree anyways, and the tree JSON representation becomes too huge to be manageable.

In the end, it depends on what sequences you analyze - larger genomes and lower quality sequences require more memory. As well as how much memory you have available on your computer. Closing unused browser tabs (especially other Nextclade tabs) and other programs might help to free up the memory (up to the maximum of 3.5 GBytes). In Nextclade's settings you can reduce number of parallel threads and turn off extra markers in sequence views to reduce memory consumption. You can use Chrome's task manager (Menu -> More tools -> Task manager) as well as system memory monitoring tools to keep track of memory and CPU usage.

Additionally, you can split your inputs into chunks and analyze them separately.

If you need large-scale analysis, our recommended solution is to run Nextclade CLI, which can analyze virtually unlimited number of sequences (especially if the Auspice tree JSON is not requested in the outputs). It uses less memory and is much faster. It is not as convenient though, does not have any visualization (but you can use Excel on the TSV output file) and requires some command-line skills.

@ivan-aksamentov ivan-aksamentov added t:ask Type: question, request of information 1 and removed t:bug Type: bug, error, something isn't working good first issue Good for newcomers help wanted Extra attention is needed needs triage Mark for review and label assignment labels Sep 23, 2023
@ryhisner
Copy link
Author

Thanks. I always have a million tabs open, so maybe I need to change that. Despite reading about 200 pages on the topic, I have zero command-line skills, so using the CLI isn't really an option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t:ask Type: question, request of information 1
Projects
None yet
Development

No branches or pull requests

2 participants