100% disk access and 100% RAM usage for no reason, completely blocking my ability to work

[aaronfross]

Show-stopping performance issue here! I am completely blocked from being able to work at all. Premiere is currently using 100% disk access and 100%+ memory usage, sitting idle, doing nothing!

In Premiere Pro 2024, I opened a project originally created in v2023. Was prompted to convert the file format. After doing so, disk access on the drive where the video files are stored immediately skyrocketed to 100%. It stayed that way for a very long time. Two hours later, the drive was still being hammered to death. Completely unable to use Premiere at all, it was dead in the water because it couldn't play any files. CPU usage was near zero.

Resource Monitor showed Premiere reading the source footage files. If it was trying to build peaks and caches, it did so with extreme inefficiency.

Even worse, after closing the project, disk access persisted at 100%. Resource Monitor showed the same few source footage files being read. Eventually Premiere got tired I guess, or it felt it had punished the drive enough, and eventually petered out after about five minutes.

Other projects opened normally, there were a few seconds of heavy disk access but then it went back to normal -- zero access when Premiere is idle.

Of course I restarted the Windows 10 PC, but that made no difference.

Updated to 2024.5, re-converted the original v2023 project file, but that made no difference.

Deleted all Media Cache files through Preferences, but that made no difference.

I did notice that projects using footage encoded with Blackmagic MJPEG codec hit the drive a lot harder than projects using footage encoded with NVIDIA NVENC H264. I guess H264 files don't need caches at all?

The problematic project has about 100 source files, TRT 14 hours, all encoded with Blackmagic MJPEG. Totaling about 400GB, which is kind of a lot, I know. It's showing them all as offline while it hammers the hard drive, presumably trying to build caches and peaks. So one might conclude that there's a performance issue with the codec? It's not hardware accelerated. But there was no issue whatsoever when I originally edited this project in Premiere 2023. And again, CPU usage is near zero, so the problem seems to be completely about hard drive access.

Contrast this with another project using the same codec, with only ten files totaling 3GB, TRT 30 minutes. Even after deleting all cache files, the smaller project takes ~15 seconds to load. The larger project does not finish loading even after two hours. The math here doesn't seem to add up. I could imagine that 400GB would take a half hour at most. Not multiple hours.

I did update the Blackmagic Desktop Video software, which includes the MJPEG codec. Not really relevant, though, because Premiere has native support for MJPEG. It just won't load the audio in the AVI files created by Blackmagic unless the Blackmagic codec is installed. Not a concern for me here because I'm not even using that audio. But updating the Blackmagic software made no difference.

Any way you slice it, a project should not take hours to load, even if the source footage is 400GB. I am really not accustomed to this sort of behavior. Sony Vegas never made me wait for hours while it ground my hard drive to dust, no matter how large the source footage folder was. If this is supposed to be speeding up my workflow, I regret to have to say that it is the opposite of that. It has completely shut me down.

I really don't want to erase my preferences, since it was a huge PITA to get Premiere set up to be even remotely close to an efficient workflow.

So what am I supposed to do here? Reinstall v2023? I doubt that would make any difference, as it seems the issue is just massive inefficiency in building the cache files.

Is there any option to NOT build these cache files? Or to control how many files are read simultaneously? Maybe if it was only reading one file at a time it wouldn't be fighting itself for limited bandwidth?

BTW, the hard drive is not super fast, but it is a 7200 RPM Western Digital platter, internal. Again, if I were to do a backup, I would expect that 400GB would take maybe a half hour to transfer. Not multiple hours!

And why are these caches temporary external files in the first place? If they take so long to build, shouldn't they be persistent? If not stored in the project file, at least stored next to the source footage? That's an option for the peak files. Why not the cache files? Why set things up for failure like this?

In the end, I let the computer sit for hours until the disk access went back to zero. All of the footage in the bins finally read as being found, not pending, and all of the statistics were visible. Tried to access the timeline and BOOM, disk access went back to 100%. What the actual frak?!?! And now RAM usage is pegged at the maximum, too! I have 32GB RAM and have 6GB reserved for other applications. Premiere has gone totally rogue here, consumed 100% of disk time and 100% of memory. Now it's using the page file, completely runaway process, it's currently up to 44 GB and still rising. SITTING IDLE, DOING NOTHING.

I turned off the timeline thumbnails with the super secret hotkey. No change. Disk access still pegged at 100%. RAM usage still greater than the maximum I set aside for Premiere. What is Premiere even doing? It's not building caches, it's not playing the timeline, it's just sitting idle. This is OUTRAGEOUS! Resource Monitor says it's still accessing those source files. But WHY???

How do I get back to being able to actually work?

This is just shocking!!! It's acting like malware!

[Alex367466572b5i]

CS6 can work with a DV AVI on a HDD, and do realtime playback, and 2024 needs PCIe NVMe and proxy/transcoding...
What's next?
And there are hundreds of such nuances, with the same acceleration of 3 times the ProRes, etc.

[aaronfross]

"As noted, the thing that intrigues me is that Premiere is at all usable ... period ... on that ancient piece of machine."

That is so incredibly not helpful and shows both ignorance and elitism wrapped up into a single sentence.

I customized this Dell PC, which was new in 2017, by upgrading the power supply, graphics card, hard drives, memory, and peripherals. It works very well for everything I need it to do. The CPU is not the fastest in the world, but I am still doing tons of professional work with it. 3D animation, audio production, and yes, video editing. Keeping the GPU relatively up to date is far more important than the CPU.

This very PC worked fine to edit those very same AVI files two years ago. The PC didn't get slower. Premiere introduced a bug that completely broke the process.

Every release of every Autodesk product gets faster and more efficient. They actually care about such things. Adobe definitely is the opposite, every release of every product gets slower and less efficient.

The idea that a PC more than a few years old is useless is just false. Literally the only reason a PC would get slower with time is because software companies load it down with more and more inefficient code.

Keeping the system in top running order has always been a high priority for me. Sometimes it is a challenge to do so, especially with Windows constantly burdening the system with new and unnecessary features. But I can tell you that, sitting idle, this PC uses 1% of CPU. I run a very tight ship here, so that my hardware can last much longer than the conventional wisdom of disposable technology would have us all believe.

[R Neil Haugen]

You have amazing computer hardware skills, and for that I definitely commend you.

But ... the very language code that CPUs use changes over time. That's not a theory, it's reality. And yes, it is frustrating that these machines get outdated so fast. I cannot stop that, nor am I "elitist" or anything. 

The Adobe apps keep several generations of code in their programming ... which is part of the reason they are so complicated and realistically, can 'break' at times. The program is constantly choosing the right code for that machine at that task. Your machine is sixth generation CPU, the current Intel generation is 14. That is long out of date. And yes that does matter.

Code is code. It changes with new CPUs. 

I'm simply a realist. What works ... works.

That CPU hasn't had any updates even available for what, two years now? I'm amazed it works the app it does. As noted, my far newer (and in 2019 very powerful) laptop simply can't run anything newer than Resolve 17 in a useful manner. Though it still runs both the 24.x shipping and public betas fine.

I wish it could handle Resolve, but oh freaking well. That ship sailed a couple years ago. I'm on R19 public beta there on my main machine. My spendy 2019 laptop powerhouse can't go past R17 though.

[Alex367466572b5i]

They write to you that the same problem exists on the i5-13500 (or do you already have a Core Ultra 200 in your PC?)... it has surfaced before ...
The problem is with the disk subsystem, there is a problem with the HDD and it is not on the same PC with PCIe.
What does the code have to do with it?

[R Neil Haugen]

Computer code is everything in a computer. It's the language used for all processes. The code ..  the "language" for telling the machine to anything ... changes to a certain extent with each CPU generation. As the reason for the new generation chip is to do things not possible with the previous ones.

And of course over time they find more efficient ways of making the code itself. So even for current chips, things can and will change.

The programs are all built using that code.

[Cratin24]

Once I upgraded, I have had the same problem opening any project. My network would jump to 100% and stay there for no reason, and only when I used Premiere. Theonly way I was ablt to fix the situation and start working again was to reinstall v23.0.  Once I went back to that version of the software, everything opened up immediately and started to work again.  It is something with these newest versions of Premiere.  I edit off a QNAP on a 10Gbe connection, and it has worked flawlessly for 5 years now, until this.  All drives are good. I am on a PC with an AMD Ryzen Threadripper 3.8Ghz 24-core and 128 Gb of RAM.

[Jarosław5C73]

I have the same issue after newest update. Is there anyone who fixed this or found solution ? 

[Cratin24]

The only way I got it to work was to go back to V23.0.  Since then I have downloaded V25 and it seems to work like it did before.

[Neil_BR]

There is definitely something going on. In my case it is a heavy project but this is the first time I see it behaving this way. I "fixed" it by updating NVIDIA drivers (don't know if this mattered since GPU did not spike), then reloaded Premiere, waited for the GPU profiling to complete, then kept a timeline open but stopped for a few more minutes. In my case CPU and RAM spiked frequently in the task manager while the status bar stayed empty. After 5 minutes and without warning, it suddenly came back down to 0.1% CPU and about 6GB RAM usage, which is typical. Since then I've been editing for a couple of hours without a hiccup. This looks like unreported background activity, the kind of background activity you expect from automatic OS updates but never inside Premiere Pro. On a sidenote, I find it very suspicious that we're still on 25.0.0 after all these weeks. Adobe, please look into this!