...
- Documented component level benchmark compared against previous/equivalent version without the new development
- Does this comparison result in performance degradation (Might need a quantitative threshold here? Something high enough to be out of the noise, but low enough to trigger a look. A lot of little increases can cause death by a thousand cuts so might want to keep this fairly low)
- Group leaders can often make the judgement call at this stage if performance negligible.
- Define standard benchmark and collect data on target machines.
- Will code effect overall ACME performance?
- Estimate based on component fraction in target production configurations
- Do alternative algorithms and data structures need to be considered?
- Quick code inspection to evaluate for showstoppers, particularly for developments in targeted performance regions.
- Does the computational cost vs science improvement trade-off need to be weighed by the ACME Council?
- If code performance exceeds threshold, for performance degradation, may elevate to Deep Dive and Council vote to evaluate whether science justifies expense
...