2025 Layout Speed -- Large Model compared to 2024

Hi all,

I am so loving the improvements to 2025 for SketchUp. My large models seem to be snappier. When guiding owners and production staff through complex details there is nothing worse than having the model freeze. So thank you Trimble and crew!

However, Layout seems to have taken a performance hit!

Opening the same documents from 2024 in 2025 and I am locking up Layout. My file size is close to 300mb.

In 2024 it works. I keep my crew happy with the docs that are needed on our production floor, but 2025 so far is rough.

I will post what I am learning as I work to get 2025 up and running.

2 Likes
Welcome Quit Layout Open Arch D Template Lag at Welcome Dialog Scrolling Settings Settings Lag, General Right Click Menu Large File Open
225 mb
Save Large File Update Model Reference Move View Port ( Context Cursor) Move Viewport ( m or click move icon) Zoom Mouse Wheel
2024 27.5 16.33 1 0 0.56 0 0 19.91 8.2 12.84 0-1 0-1 0
2025 39.5 25.8 1.5 1-3 1-2 1-2 0-5 21.8 8.67 8.37 5-10, LockUp 0-1 5-10, LockUp
1 Like

I’d imagine a lot of peeps will suggest using draft mode in LayOut so it doesn’t PassOut! But irrespective, that’s a fair reduction in processing!

I can test on M1, M3 Pro Max, and M4 Pro. I will see what figures I get.

I’m sure @Barry would want to try as well.

1 Like

I am on M1 Max 32gb ram. Did equal comparison between my 2024 to 2025 version. I am not using the draft mode with 2024.

Also, I am using the “Construction Documentation Style”

A couple of notes here:

I did the test after a full reboot, and only running SketchUp and Layout.

  1. Caching; there must be some sort of caching going on, as my settings lag, welcome screen dialog lag have dissipated and are now on par with 2024. The same with file open times. This happened not after another re-boot, but after opening and closing the app, and files, multiple times.

  2. When using the cursor inference over a viewport to get the move cursor, I get a glitchy red diamond and line, as if it’s trying to do inference. Then a delay of 1+ second to move the view port. This does not happen if I use the menu bar to select the move tool, or the “m” key. Then it is responsive.