F5F Stay Refreshed Hardware Desktop The rendering process is consuming too much time (assistance needed)

The rendering process is consuming too much time (assistance needed)

The rendering process is consuming too much time (assistance needed)

S
SloPeZ
Junior Member
33
08-14-2018, 05:46 AM
#1
Hello everyone. My render time is slowing down significantly. I've tried rendering in NVENC with GBU on RTX 2080 and on a CPU with 9,3395x 16 cores and 32 threads—still quite capable for rendering. However, the issue persists across all setups. I'm unsure what's causing it, but I've noticed my CPU load fluctuates: it drops, rises, then goes down again. After switching to GPU rendering, the same pattern appears. I've checked two renders with 2.5 GB video and seen similar behavior on both NVENC GBU tests and CPU tests.
S
SloPeZ
08-14-2018, 05:46 AM #1

Hello everyone. My render time is slowing down significantly. I've tried rendering in NVENC with GBU on RTX 2080 and on a CPU with 9,3395x 16 cores and 32 threads—still quite capable for rendering. However, the issue persists across all setups. I'm unsure what's causing it, but I've noticed my CPU load fluctuates: it drops, rises, then goes down again. After switching to GPU rendering, the same pattern appears. I've checked two renders with 2.5 GB video and seen similar behavior on both NVENC GBU tests and CPU tests.

L
Luckydido99
Member
102
08-14-2018, 10:54 AM
#2
You're using a 2080 and 3950 graphics card, working on a specific app, and you're checking your available RAM. Your GPU has 8GB of VRAM. You mentioned using nvenc for encoding but not for actual rendering.
L
Luckydido99
08-14-2018, 10:54 AM #2

You're using a 2080 and 3950 graphics card, working on a specific app, and you're checking your available RAM. Your GPU has 8GB of VRAM. You mentioned using nvenc for encoding but not for actual rendering.

S
SxBALLER
Member
51
08-21-2018, 01:00 AM
#3
I tried Vegas Pro 18 twice—once using NVENC and once on the CPU. All of them took a long time to render, and I noticed a zigzag pattern in the load graph going up then down.
S
SxBALLER
08-21-2018, 01:00 AM #3

I tried Vegas Pro 18 twice—once using NVENC and once on the CPU. All of them took a long time to render, and I noticed a zigzag pattern in the load graph going up then down.

C
CleanerHook54
Junior Member
39
08-23-2018, 07:32 AM
#4
32 ram
C
CleanerHook54
08-23-2018, 07:32 AM #4

32 ram

R
Reign_OF_Pain
Member
165
08-25-2018, 03:49 AM
#5
Have you previously processed comparable items on this device using that application? I'm trying to clarify what you're referring to by "taking too long."
R
Reign_OF_Pain
08-25-2018, 03:49 AM #5

Have you previously processed comparable items on this device using that application? I'm trying to clarify what you're referring to by "taking too long."

L
131
08-25-2018, 06:40 AM
#6
The time required depends on your system's speed and workload, but generally rendering 2.5 GB on a Ryzen 9 3950 with 32 RAM can take anywhere from a few seconds to a couple of minutes, especially if you're using a modern GPU and efficient settings.
L
lunathealicorn
08-25-2018, 06:40 AM #6

The time required depends on your system's speed and workload, but generally rendering 2.5 GB on a Ryzen 9 3950 with 32 RAM can take anywhere from a few seconds to a couple of minutes, especially if you're using a modern GPU and efficient settings.

B
beichner
Senior Member
447
09-01-2018, 06:06 AM
#7
If that 2.5gb is a single pic there’s gonna be a ton of memory swap. In my day it would have taken days in photoshop. Those days were long ago though. This also isn’t photoshop so that likely isn’t just one image. The big thing that slows rendering down is swap. Having to effectively use drive space as memory. I don’t know whether that is happening or not. The solution if it is would be to add more ram. Ideally enough ram that the thing doesn’t use swap any more, and failing that a faster storage system. The answer was often both because the thing actually needed more memory than it was possible to add. If you’re hitting your swap a lot during this rendering (this can be checked) you might need more memory.
B
beichner
09-01-2018, 06:06 AM #7

If that 2.5gb is a single pic there’s gonna be a ton of memory swap. In my day it would have taken days in photoshop. Those days were long ago though. This also isn’t photoshop so that likely isn’t just one image. The big thing that slows rendering down is swap. Having to effectively use drive space as memory. I don’t know whether that is happening or not. The solution if it is would be to add more ram. Ideally enough ram that the thing doesn’t use swap any more, and failing that a faster storage system. The answer was often both because the thing actually needed more memory than it was possible to add. If you’re hitting your swap a lot during this rendering (this can be checked) you might need more memory.