CPU 14700K not undervoltage applay
RTX 3090 - NVIDIA FE
Vertion Rhino 8 SR29
RUNS
I FIRST RUN
Rhino Render [Optix]
slider sharpness to 10/10
45 segundos inicio Inizia
2:49 min 1000 samples
8:22 min 4000 samples
5.5 GHz CPU
100% GPU 67°
3255 x 1968
100% Windows Scaling
II SECOND RUN
Rhino Render [Optix]
slider sharpness to 10/10
45 segundos inicio Inizia
2:56 min 1000 samples (youtube video on the backgrund)
10:40 min 4200 samples
5.5 GHz CPU
100% GPU 67°
3255 x 1968
100% Windows Scaling
III CPU RUN
Rhino Render [CPU] <----------<<< special: slow
slider sharpness to 10/10
45 segundos inicio Inizia
2:56 min 45 samples (youtube video on the backgrund)
4.7 GHz CPU
100% GPU 45°
3255 x 1968
100% Windows Scaling
IV LESS SHARPNESS
Rhino Render [Optix]
slider sharpness to 9/10
45 segundos inicio Inizia
1:xx min 1000 samples (youtube video on the backgrund)
3:59 min 4200 samples
5.5 GHz CPU 100°
100% GPU 67°
3255 x 1968
100% Windows Scaling
UNDERVOLTING 1
Rhino Render [Optix]
44 segundos inicio Inizia
2:49 min 1000 samples
8:22 min 4000 samples
5.5 GHz CPU
100% GPU 67°
3255 x 1968
100% Windows Scaling
RTX 5090
CPU 14700K not undervoltage applay
RTX 5090 - ZOTAC GAMING AIO
Vertion Rhino 8 SR29
RUNS
I BIG RESOLUTION CUDA
Rhino Render [CUDA] <----------<<< special: slower CUDA
slider sharpness to 10/10
12 segundos inicio Inizia
2:37 min 1000 samples
N/A min 4000 samples
5.5 GHz CPU
100% GPU 51°
4522 x 2605 <----------<<< special: slower big resolution
138% Windows Scaling <----------<<< special: slower big size
II BIG RESOLUTION OPTIX
Rhino Render [OPTIX] <----------<<< special: faster OPTIX
slider sharpness to 10/10
12 segundos inicio Inizia
1:43 min 1000 samples
6:05 min 4000 samples
5.5 GHz CPU
100% GPU 53°
4522 x 2605 <----------<<< special: slower big resolution
138% Windows Scaling <----------<<< special: slower big size
III OPTIX LESS SHARPNESS
Rhino Render [OPTIX]
slider sharpness to 9/10 <----------<<< special: faster some blur
12 segundos inicio Inizia
0:53 min 1000 samples
2:44 min 4000 samples
5.5 GHz CPU
100% GPU 48°
4522 x 2605 <----------<<< special: slower big resolution
138% Windows Scaling <----------<<< special: slower big size
IV RHINO RENDER Note: hard to start Rhino window Rendering, nicer in black areas, hi alaising definition
Rhino Render [OPTIX]
slider sharpness to 9/10
2 minutos inicio Inizia
1:52 min 1000 samples
6:40 min 4000 samples
5.5 GHz CPU
100% GPU 51°
3840 x 2160 <----------<<< special: slower big resolution
138% Windows Scaling <----------<<< special: slower big size
V SAME AS 3090 RUN IV Note: same rendering settings as RTX 3090
Rhino Render [OPTIX]
slider sharpness to 10/10 <----------<<< special: slower
12 seconds inicio Inizia
1:22 min 1000 samples
4:05 min 4000 samples
5.5 GHz CPU
100% GPU 47°
3159 x 1860 <----------<<< special: Raytraced viewport in 4k resolution
100% Windows Scaling <----------<<< special: back down to normal
VI SAME AS 3090 RUN IV Note: same rendering settings as RTX 3090
Rhino Render [OPTIX]
slider sharpness to 9/10 <----------<<< special: faster
12 seconds inicio Inizia
0:45 min 1000 samples
2:27 min 4000 samples
5.5 GHz CPU
100% GPU 49°
3255 x 1971 <----------<<< special: SIMILAR AS 3090 RUN IV
100% Windows Scaling
Rhino 9 WIP
VII RHINO 9 WIP Note: Rh9 WIP same rendering settings as RTX 3090
RHINO 9 WIP Vertion: (9.0.26084.12305, 2026-03-25)
Rhino Render [OPTIX]
slider sharpness to 9/10 <----------<<< special: faster
10 seconds inicio Inizia
0:34 min 1000 samples
1:43 min 4000 samples
5.5 GHz CPU
100% GPU 49°
3194 x 1967 <----------<<< special: SIMILAR AS 3090 RUN IV
100% Windows Scaling
You can make rendering even faster by relaxing the threshold for adaptive sampling. You can find the settings in the advanced section. By default the threshold for adaptive sampling is set to 0.01 (1% “error”), but I have found that in the majority of cases 0.1 is more than enough. Since most renderings are stills and not animations most of the viewers probably can’t even tell the difference - a difference that is visible only when you actually compare pixels for pixels and create a difference from two subsequent renders (of the same scene with completely same settings).
So ensure in the advanced settings adaptive sampling is enabled (should be by default) and that you increase the threshold. I would say 0.1 to 0.15 is typically still good. For really quick tests (when you’re look-deving) you could go even higher, but then you’ll probably start seeing artifacts. Yet it should still give good result for getting lighting, material, overall look and feel done before you tighten up that threshold for an actual final render.
what are you suggestions for nb of iterations. In the rare case i render a scene (mostly just a display mode) it stop noticing a change after so 30 iterations. I normally just run a test and downgrade from that count.
What are you suggestion for size. I use 4k monitor so it defaults to that size, but can imagine that AI upscaling can also boost performance in terms of time when rendering is a lower pixel count and do post-prosssing upscaling.. And do you render all in one go, or render different layers (occlusion, specular, etc…) and do a join in photoshop?
@AlanMattano Have you tried the Cuda rendering performance on WIP9?
Becasue from what I remember Cycles was updated entirely in W9 so the improvment you see may not directly related to the Cuda/Optix system but to the Cycles version.
Oh wow! We live in a world where 10 minutes is a long time to render.
I’m quite young, but even now I recall the pain of waiting for Scanline or Mental Ray taking 4 days to do a 1080p render on my Pentium 4 Hyperthread.
Every time I use Cycles, my memory works such that I am still mindblown about how fast OptiX is. I am fortunate to have a 4090 and a 4070 Super, but OptiX is so fast, I tend to just use the Super. I am even more astonished when I watch bella at work, just on the CPU and how fast that is, despite sometimes wanting it even faster. It seems still surreal.
Rhino Rendering Speed Tips (Real Gains, Not Hardware)
Huge difference.
Main line: