Extension of the basic BRIG - like rings and annotations to some more specific applications:
For long running tasks we want to:
Adding the --splits argument to genomad execution to reduce memory footprint for now. See if timeout limits have to be adjusted. These arguments can all set through the FastAPI settings and when deploying the stack through the docker/brick.env stack configuration variables.
Intensive bioinformatics tasks are not meant to run in task schedulers, especially considering resource management. Need a better solution also for other projects, any suggestions welcome!
Extension of the basic
BRIG- like rings and annotations to some more specific applications:abritAMRgeNomadgeNomadprediction class selectionFor long running tasks we want to:
maybe at a later stage, working relatively smoothly nowApp: perhaps we need a job table which contains a log of submitted and completed/failed jobsServer: keep a copy of the output tagged by reference sequence or similar to avoid redundant re-computingServer: limit threads in case of high load on these tasks, both on Celery workers and as setting for subprocessesServer: limit worker container memory for tasks, or implement proper workflow scheduler for intensive pipelinesServerProfile geNomad memory consumption to set limits on worker containerAdding the
--splitsargument togenomadexecution to reduce memory footprint for now. See if timeout limits have to be adjusted. These arguments can all set through theFastAPIsettings and when deploying the stack through thedocker/brick.envstack configuration variables.Intensive bioinformatics tasks are not meant to run in task schedulers, especially considering resource management. Need a better solution also for other projects, any suggestions welcome!