I have not tested this yet but I’m wondering if there are any performance / memory issues that could occur when you have several tabs open. Is there any logic in place that mutes or puts tabs in a sort of inactive state when they haven’t been used for x time to limit performance / memory issues?
I was concerned about this, but looking at my server I have not noticed any considerable cpu hit. maybe from a browser point of view there maybe an effect
Thanks, that’s good to know. I also just noticed when switching tabs that it reloads the preview panel each time, so that may indicate that not much, if anything, is kept in memory from the tabs you’re not actively working on.
As you all are discussing here, since only one tab is really “open” at a time, there really aren’t any more performance considerations from the server standpoint as old versions of Pro had. From a browser perspective, obviously having many assets open at a given time could lead to some slowdown, but I’ve personally had instances with dozens of tabs open and haven’t noticed any considerable lag.
1 Like
Thanks Kory, that’s good news. Looks like the performance part is well taken care of then.