From previous comments by the developers, I had hoped to see improved performance in this version, especially when switching to Scrivenings view.
Have to say, I can’t detect any, and I still get the “Not responding” error while waiting for Scrivener to display a chapter (7 files, c.30,000 words)
However, it does feel as if simply switching from one document to another (i.e. clicking on the binder so that the document loads into the active editor window) is a bit snappier.
Out of curiosity, where do you see the slowdown?
I’m still on the last version before RC1, but a 100K word document seems very snappy on my ultrabook.
I tried Scrivening mode as well as jumping between individual chapters.
@jje, do you have a lot of footnotes or comments to your texts? I find that having many slows down things on my Mac (i7 processor with separate graphics processor and plenty of RAM).
Mark
The speed improvements were about loading many documents in the Outliner.
To detect the bottleneck, you might try splitting the document into smaller bits and detect which is causing the delay, it could be a big image, or many Inspector Notes. This should be only on initial loading though.
My mistake perhaps; the outliner is certainly very snappy, but as I never use it, I can’t say how much better it is.
The problem is switching to Scrivenings view. I have folders for each chapter, which are split into several documents (usually 3-5 per chapter, corresponding to sub-headings). The chapter are long (20-30,000 words). When I click on the folder in the binder, the whole chapter loads in Scrivenings view. There is a very noticeable delay (5-6 seconds) while the chapter loads. If the chapter is really long, the message “Scrivener is not responding” appears alongside the project title at the very top left-hand corner of the Scrivener window. There are a lot of footnotes (it’s an academic book): as many as 300 in a chapter.
Once I’ve loaded a chapter, if I switch to another then back to the first, the original one loads slightly faster (by a second or two), but is still sluggish.
Just FYI, my PC has an Intel Core i7-6700 CPU @ 3.40GHz, 16Gb of RAM. Windows and Scrivener run on a Samsung SSD (Evo 850, 500GB). The project is on a generic mechanical hard drive (SATA-III 3.5" HDD, 6GB/s, 7200RPM, 32MB cache). Running 64-bit Windows 10 Home (and 64-bit Scrivener). So, not exactly state of the art, but I would think sufficient to cope with Scrivener.
Your PC is fine. The ~300 Inspector notes in a document are most likely causing the speed loading problem. Each Inspector Note is an RTF document on its own (not on the HDD but still within the RTF format), which needs loading and parsing through the RTF engine.
Moving your project to the SSD, might speed up things a bit, but not much I believe. If you do not spot any difference, I would move it back to the HDD.
Another solution is probably working with a shorter set of files or even one file at a time, instead of 3-5 long files. Your files are long enough to work on each of them separately. Scrivenings mode is useful when you have a lot of shorter files.
Yes, inspector notes, that is what I find slows things down. My stuff is all on an SSID (2TB, so not a space problem there), my i7 is clocked at 2.4 GHz with 16GB RAM (currently about 10GB free) and separate graphic processor and VRAM … so this MBP is no slouch!
But even in single document mode, lots of inspector comments still slow it down.
Mark
It was the speed of SSD over the HDD, which I had in mind, not the free space available.
I do realise that … sorry for the unnecessary information.
Mark
I have the same problem. The old 1.29 (or whatever it was) was very fast in switching (near-instant) between document view and outline view. The new version, updated as of this morning (Version: 2.9.9.1 Beta (886698) 64-bit - 05 Apr 2020) still takes a long time to show the outline view. And it’s not just waiting for it to show up, once it’s already rendered, it will take a long time to resize a column (it throws up the circle and says not-responding) or adjusting Binder/Inspector sidebars. Just anything that causes it to re-render the outline. One especially bad thing is if you pause while you’re resizing a column (let’s say) and then continue resizing. It seems to re-render it more than once for an extra-long delay.
It’s very painful. I have 97 documents (around 8 or 10 of them are just markers for me in the binder, so the documents themselves are blank). I have no sub-folders inside the manuscript folders. Just the list of single documents.
UPDATE: I have a 6-Core AMD system with SSD drive (though I use Dropbox for storing my novel data, 1GB internet connection), gaming video card-- system designed for gaming.
I have no footnotes, no comments or anything like that. I do have images and notes in the inspector, also some keywords and labels. However, I had no problem with switching from a document view to the outline view in the old version of scrivener. Whatever the problem is, it’s unique to the new version.
MORE INFO:
I just updated again to version Version: 2.9.9.2 Beta (887454) 64-bit - 06 Apr 2020.
The extreme sluggishness / not-responding bit is still there when I switch from a regular file to the outline. I counted (one-Mississippi style) 15 seconds from clicking on the outline until render.
The FIRST time I switched BACK from the outline to one of the flat files, there was a similar delay. I don’t recall that happening before, but perhaps it did and I just didn’t notice. However, upon subsequent attempts of switching BACK it happens quickly, as expected. BUT, it always takes a long time going INTO the Outline mode.
If I had any space on my SSD, my Scrivener project files would be there, but Windows and all my software, etc. leaves me with only 110Gb free, whereas my Dropbox folder is well over 300Gb! So, until I can afford to replace the two mirrored HDDs where Dropbox lives…