SImA is configured with 3 batch analysis job queues: SImA quick, SImA default and SImA debug. Each queue is configured with a "per task" resource reservation of CPU and RAM, which allows users to select the appropriate resource for the assay type. The table below details the "per task" resource allocations of each queue.
Job Queue |
CPUs |
RAM (GB) |
Use Case |
SImA quick
|
1 |
5 |
Basic analysis, e.g. Cell Counting 2D. |
SImA default | 2 | 10 |
All analysis including complex analysis, e.g. Cell Painting. |
SImA debug | 2 | 10 |
Troubleshooting only. |
Each well within a plate is processed as an individual "task" during batch analysis execution. Given a 384 well plate, 384 image processing tasks will be executed. The number of tasks/wells which SImA is able to process in parallel is dependent on the SImA servers CPU and RAM reserves, as well as the job queue which is used to submit the job.
For example, given a SImA server with 10 CPUs and 50 GB of RAM:
- If the analysis job was submitted using the SImA default job queue (2 CPUs / 10GB per task), SImA could process 5 tasks/wells in parallel. Once the first 5 wells have been analysed, the next 5 wells will be processed, and so on.
- If the analysis job was submitted using the SImA quick job queue (1 CPUs / 5GB per task), SImA could process 10 tasks/wells in parallel. Once the first 10 wells have been analysed, the next 10 wells will be processed, and so on.
The SImA quick job queue requests less compute power than the SImA default queue, and because of this, allows for a greater number of wells to be processed in parallel. This queue is ideal for quickly processing basic image analysis pipelines, but may be under resourced for complex analysis tasks.
The SImA default queue requests more compute power than the SImA quick queue, and as such is better suited to general and complex image analysis pipelines.
For basic 2D analysis work the SImA quick queue may provide the best performance. For more complex 3D analysis and/or cell painting assays, the SImA default queue may be optimal.
Comments
0 comments
Please sign in to leave a comment.