Raise max_sequences limits for larger alignments - #863
Merged
Conversation
Sizes derived from the DM3 timing calculator (power-law runtime fits, timingEstimates.js) targeting a ~12h budget at 1000 sites on the 32-core backend config: base (fel/meme/slac) 5000 -> 10000 fubar 10000 -> 25000 contrast-fel 2000 -> 5000 absrel 1000 -> 2500 relax 1000 -> 2000 busted 1000 -> 2000 bgm 1000 -> 1500 GARD and multi-hit intentionally left at 1000 (runtime is superlinear in taxa; they are the methods most prone to walltime timeouts). max_sites (base 32000) unchanged; real uploads top out ~12k.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Raises per-method
max_sequenceslimits so users can submit larger alignments. These caps hadn't been revisited in years and were the practical constraint on datamonkey.org (most methods stopped at 1000 sequences).Values were derived from the DM3 timing calculator (
timingEstimates.jspower-law runtime fits), inverting each method's equation to find the max sequences finishing within a ~12h budget at 1000 sites on the 32-core backend config.Left unchanged: GARD and multi-hit stay at 1000 — runtime is superlinear in taxa and they are the methods most prone to walltime timeouts.
max_sites(base 32000) unchanged; real uploads top out ~12k.Note: these limits assume the backend runs methods at ~32 procs (matching the production config); at lower core counts the larger MEME/BUSTED/RELAX jobs would risk walltime timeouts.