AWS omics documentation change
Summary
Added CPU headroom recommendation to resource allocation guidance
Security assessment
Change improves reliability guidance for resource allocation but does not address security aspects.
Diff
diff --git a/omics/latest/dev/workflows-run-errors.md b/omics/latest/dev/workflows-run-errors.md index 05fed4015..09e6193f7 100644 --- a//omics/latest/dev/workflows-run-errors.md +++ b//omics/latest/dev/workflows-run-errors.md @@ -50 +50 @@ When developing new workflows, runs or specific tasks could become "stuck" or "h - * Provide appropriate memory and CPU allocation to your tasks. Analyze the [CloudWatch logs](https://docs.aws.amazon.com/omics/latest/dev/monitoring-cloudwatch-logs.html) or use the [Run Analyzer](./workflows-run-optimize.html#workflows-run-analyzer) on successfully completed runs of your workflow to verify you have optimal compute allocation. Use the Run Analyzer `headroom` parameter to include additional headroom, ensuring processes have sufficient resources to complete. You should have at least 5% headroom of allocated memory for background operating system processes. + * Provide appropriate memory and CPU allocation to your tasks. Analyze the [CloudWatch logs](https://docs.aws.amazon.com/omics/latest/dev/monitoring-cloudwatch-logs.html) or use the [Run Analyzer](./workflows-run-optimize.html#workflows-run-analyzer) on successfully completed runs of your workflow to verify you have optimal compute allocation. Use the Run Analyzer `headroom` parameter to include additional headroom, ensuring processes have sufficient resources to complete. Include at least 5% headroom in allocated memory and CPU, to account for background operating system processes.