College of Information ScienceComputing Resources Working Group · Point people: Barney Maccabe and Greg Chism

Optional compute estimate¶

Supplemental reference · Browse supplements · Current report

Start with the short needs brief. Use this optional calculator only when you can estimate the workload; unknown technical quantities belong in the brief, not as invented numbers. Numbers are editable examples, not measured demand, provider credits or an award. No data is uploaded or saved by this tool. Enter counts and requirements only, never private records.

40-student example loaded; edit the assumptions below.

1. Purpose and permissions

PurposeWork patternData classInput basisA selection is self-reported, not verified evidence.

2. Workload per run

People or independent groupsEach gets the per-week runs below.Active weeksCourse or research working period.Runs per person / weekUse the busiest representative workload.CPU-only wall hours / runExclude GPU-only work; include interactive idle time if allocated.CPU cores / runConfigured/allocated, not assumed full utilization.RAM GiB / runInclude the whole process/container.GPU wall hours / runSet 0 for CPU-only work.GPU devices / GPU runA visible/shared device is not automatically a full physical GPU.VRAM GiB / deviceA fit requirement, not GPU-hour conversion.Simultaneous CPU jobs/sessionsUp to the participant/group count.Simultaneous GPU jobsCannot exceed the overall peak.Retry / variation allowance %Applied to runtime totals only; 0–100.

3. Storage and support · editable defaults

3. Storage and support

Shared input data GiBOne shared copy; avoid per-person duplication here.Working files GiB / personHome/workspace allowance.Total output data GiBAcross this whole scenario.Independent backup copiesBeyond active data; 0 requires a recovery decision.Retention weeksHow long files need to remain available.Potential technical-support hours / weekScope-specific estimate; no college staffing capacity is assumed.Separate TA hours / weekPotential support; not a staffing commitment.

Enable JavaScript to calculate and export, or use these formulas: runs = people × weeks × runs/week; CPU core-hours = runs × CPU wall hours × cores × (1 + allowance/100); GPU device-hours = runs × GPU wall hours × devices × the same allowance. Peak demand is separate. Storage = shared inputs + people × working files + outputs; independent copies multiply that storage.

How to use the estimate¶

This is one representative workload envelope. For different CPU/GPU groups or multiple courses, export separate scenarios and review overlap before adding totals. Continuous services need uptime-based sizing beyond this per-run model. Storage capacity does not establish throughput, preservation or a backup service.

The tool follows the benchmark helper’s runtime × workload × resource × allowance arithmetic. Use measured component results and size_access.py for the next sizing step, then confirm provider units, target replay and classroom checks. Neither the tool nor a selected evidence basis makes a request submission-ready.

Optional compute estimate¶

Your planning envelope

Route to assess

Checks still required

How to use the estimate¶