Computational workload pilot ============================ StatMedAnalysis | Original downloadable worksheet | 6 November 2026 Estimate analysis runtime and memory using a representative pilot. How to use this worksheet Define the intended full workload and the operations likely to dominate cost. Run a synthetic or approved nonidentifying pilot at several sizes in the target environment. Record elapsed time, peak memory and failures. State where extrapolation may fail because of algorithmic scaling or parallel overhead. Save a working copy and keep the original blank version. Use public, hypothetical or aggregate information only; do not enter patient identifiers, credentials or confidential records. Keep source evidence in your approved project workspace. Mark unresolved text fields UNKNOWN or NOT REPORTED with a reason; never substitute zero for an unknown count. Project/version __________________ Prepared by role/date __________________ Working fields 1. Workload dimensions Response/evidence: _________________________________________________________ ___________________________________________________________________________ 2. Hardware/runtime configuration Response/evidence: _________________________________________________________ ___________________________________________________________________________ 3. Pilot sizes and repetitions Response/evidence: _________________________________________________________ ___________________________________________________________________________ 4. Elapsed time and memory Response/evidence: _________________________________________________________ ___________________________________________________________________________ 5. Scaling relationship and uncertainty Response/evidence: _________________________________________________________ ___________________________________________________________________________ 6. Parallelism and overhead Response/evidence: _________________________________________________________ ___________________________________________________________________________ 7. Full-run limits or checkpoint plan Response/evidence: _________________________________________________________ ___________________________________________________________________________ 8. Decision and monitoring trigger Response/evidence: _________________________________________________________ ___________________________________________________________________________ Hypothetical worked case A fictional algorithm processes twice as many rows but takes four times as long, suggesting quadratic work in that range. Multiplying the small pilot time by the row- count ratio would underestimate the full run. Decision rule and limitations Treat projected runtime as a planning estimate, not a deadline guarantee. Investigate nonlinear scaling and memory limits before launching a large job. Decision _______________________ Remaining uncertainty ____________________ Next action ____________________ Owner / review date ______________________ Independent check and discrepancy resolution _______________________________ Official method or reporting reference checked 6 November 2026 https://docs.python.org/3/library/timeit.html This is an original planning aid, not an official checklist, validated instrument, clinical recommendation or certificate of expert approval. Apply the referenced guidance to the specific design and record any additional requirements.