Now that I’ve time to poke around a bit more, here’s some more specifics.
For the newly created test project, I put in another 21k words of Lorem Ipsum into a blank template. I created enough empty folders to make the Binder long enough to require scrolling, but I didn’t have the patience to start adding in tables/metadata/labels/all the extra stuff that my project has. The length of the Binder, when fully expanded, is roughly as long as the fully-expanded Binder in the S3 tutorial, though for expediency most of the text was in about 3-4 Documents wheras the tutorial had them spread out into much shorter Documents.
The S3 tutorial mentioned below is a fresh one, created in beta 2.
Expected behaviour: quick response when selecting different Documents/Folders in the Binder. The blue highlight should follow the cursor smoothly when moving from one Binder object to another, or when moving between Menu items (Navigate, Project, Documents, etc).
Actual behaviour in my project: the blue highlight (marking which part of the Binder the cursor is resting on) lags about 2-4 seconds behind the cursor. Once the highlight is in place, selecting the new Document has about a 2-3 second lag before the new Document is shown in the Editor. This lag seems to remain about the same whether the target Document is blank or has words (usually 1-2k words), tables, etc. Lag for the Menu is more inconsistent: sometimes trying to select the Menu items induce a 2-4 second lag before the blue highlight follows the cursor into the Menu or submenus. Sometimes it’s pretty quick.
Behaviour in S3 tutorial: the blue highlight smoothly follows the cursor without lag. Selecting a new binder item takes about 1 second to display in the Editor. No noticable lag when trying to select Menus or submenus.
Behaviour in test project: same as S3 tutorial. There is no lag as the blue highlight follows the cursor. When the target Document is very short (say, 1-2 lines), the new Document is displayed in the Editor immediately. When the target Document is longer (4,276 words in my test), it takes about 2 seconds to load. No noticable lag when trying to select Menus or submenus.
Expected behaviour: smooth scrolling down the Binder if Binder is too lengthy to fit onto the screen.
Actual behaviour in my project: Binder scrolling is very choppy. After I move my mouse scroll wheel, it might take 2 seconds for the scroll bar to begin moving, and even then it often won’t move all the way. It will jerkily move partway after 2 seconds, and then move the rest of the way maybe 1-2 seconds after that.
Behaviour in S3 tutorial: after fully expanding all the nested items in the Binder, there is a slight lag. The scroll bar moves partially after about 0.5 seconds, and completes the scrolling after a second movement (also about 0.5 seconds), for a total of 1 second to move.
Behaviour in test project: smooth scrolling, no lag.
Expected behaviour: when the screen is in split mode (vertical or horizontal), switching between the editors should be quick.
Actual behaviour in my project: it takes about 2-3 seconds to switch between which editor is selected (highlighted in blue). Whether the Document displayed is blank or not doesn’t seem to matter.
Behaviour in S3 tutorial: switching between Editor windows takes less than half a second.
Behaviour in test subject: switching between Editor windows is immediate (slightly faster than in S3 tutorial).
I’m starting to feel like this might be a hardware issue, or simply due to the complexity of my project, but Task Manager reports I’m using 7% CPU and 25-30% of memory, and that’s with Chrome and Discord going on in the background.
It could be due to the length and complexity of the Binder contents. My Binder in my project is rather long because I divided my novel outline into several subfolders. When partially collapsed (with only the most frequently-used parts expanded), about 1/3 of the Binder’s contents is able to be displayed on my screen at once. If I were to expand every bit of the Binder, the Binder would probably only be able to display 1/5 of the total contents. The contents are nested up to 3 levels deep (root level, subfolder, subfolder). That said, I don’t recall this lag being present in 2.9.0.1. And despite the amount of character sheets and subdocs in my Project, the total file folder is only 3.29 MB.
I posted it in a new thread and it contains my actual problem (besides the lagging mentioned in the posts up top).