Hardware Tier
Scene
M tris
Polys
5 M
Render Engine
Realtime: Eevee, Unreal. Offline: Cycles, Arnold, V-Ray, Redshift, Octane.
Quality
Samples
512
Resolution
Light bounces
6
Denoise
On
Job
frames
nodes
...
/hr
Calibration
Scene multiplier
1.00x
Tune the multiplier to match a real test render: if a known frame took twice this estimate, set it to 2.0. Estimates are a transparent heuristic, not a guarantee.
Estimated Time Per Frame
-min
single node, current settings
Total (1 node)
-
With farm nodes
-
At a Glance
Per Frame
-
one node
Total Render
-
all frames
Wall Clock
-
across nodes
Farm Cost
-
est. compute
What Drives This Estimate
Engine base (-)
Geometry (-)
Samples (-)
Resolution (-)
Render Plan
Time per frame (single node)-
Total node-hours required-
Frames per node-
Wall-clock time on farm-
Estimated compute cost-
Per frame
-
Total
-
Estimate Detail
Engine base-
Geometry factor-
Sample factor-
Resolution factor-
Bounce factor-
Texture factor-
Hardware tier-
Denoise saving-
Pro Tips
Samples scale sub-linearly. Doubling samples rarely doubles time once denoising is on. Test 256 vs 512 before committing a sequence.
Denoise hard. AI denoisers (OptiX, OIDN) let you cut samples by half or more for the same clean result.
Geometry is cheap, lighting is not. Polygon count matters less than bounces, volumetrics and complex shaders in path tracers.
Calibrate first. Run one real frame, then set the multiplier so the tool matches it. Every scene is different.