Is 2026 terribly slow because of the new database structure, or is something else going on?

Flame Flame Questions
,
1

I’ve been working on a long term project, and upgraded to 2026 a few months ago. Is it me, or does take MUCH longer to Save a Batch, or a Workspace? It’s fairly large - 100ish media clips, 25 Batches, 40 sequences, but the Batches aren’t terribly complicated - maybe 30-40 noes per Batch, but the saves are super slow… I never timed it before, but I’d guess 10 seconds? Now it’s 65 seconds every auto-save of the workspace!

I’ve seen some other threads about removing all old versions of Flame - is that recommended? I’m already “over the falls” on this one, so there’s no going back to 2025, but I’m also not super Terminal friendly, so I don’t relish copy-pasting commands I don’t understand…

2

I have not had this experience, although I have removed all traces of 2025 from the system. One thing I have noticed is that my 2026 archives open and close much faster than the 2025 archives. And by that, I mean the 2025 archives when I was still running 2025.

3

I would also say never upgrade mid-project

4

100% Agree, most of the time. I was thrilled to have a new type tool, LOL. But seriously, there’s a lot of animated text, so working in that old Text tool was a major pain point for me. WAY worse than having slow saves.

5

where is your project directory?

For me when I put it on my nas its incredibly slow to save even a single batch (5s)

6

for 2026, I’m using my RAID5 for both media and projects.

7

@davejahns - hardware RAID5 is normally set to a fixed block size.
writing many small files into large blocks is inefficient.
when you get round to it, consider using a mirrored z-raid with unspecified block size.
do not use hardware raid controllers.
also, read about sync and async and RAID5 write holes.

2 Likes