[LH3264:FIXED] a bit sluggish

I loaded one of my projects, and started working on it. Editing stuff. I noticed that loading a document the first time during a session is fairly slow. Slower than 2.9.08 was. After that first load, it becomes much quicker (which I think is due to a cache).

Not entirely sure why this is. So after using OBS to record my actions:

63 frames at 60 fps to load a 784 word document. That’s 1.05 seconds.


Same here.

This doesn’t seem to be a problem for me.
I have a project that I imported from version 1.9.7. In the Draft section over 80,000 words, over 120 documents (& sub-documents), many with 2K words or more. Response in Beta when scrolling through documents seems instantaneous. Clicking the Draft folder in outline mode takes about 1.5 seconds, but that’s fine. Clicking a document group that has many subdocuments - in outline mode - is nearly instantaneous.

Scrivener Beta
Windows 7 Home Premium
Pentium i5

Interesting. I’ve got a 100k word document, and it takes over a minute for outline mode to display for the Draft folder.

Windows 10
AMD Ryzen 1600
Nvidia GTX 1050 Ti
Plenty of HD space.

I wonder what the difference is?

Because if you’re not experiencing this delay (and it’s new for me; I did not see this in, and others are, there must be some difference.

Mind you, once I’ve clicked on a document, and then clicked on another document, clicking back on the first document is nearly instantaneous.


I fixed some of the sluggishness. I uninstalled Scrivener. Physically deleted everything remaining in the Program Data directory. EVERYTHING. For some reason, uninstalling did not remove the entirety of that directory. Not sure why. But it didn’t, not even the directories it itself had installed.

Then I reinstalled.

Mind you, it’s still a bit sluggish, but not as bad as before. Now, a document of 5k words takes well under a second to pop up, but the delay is still noticeable (at least to me).

This also seems to have significantly reduced the delay in outline view and the Binder.

Not sure why. Shouldn’t have made any difference.

I have a 380K word project that opens in just a few seconds, after which I experience no noticeable lag or delays (except when compiling :slight_smile: ). It’s made of text documents running from 500 to 6000 words each (most are 1300-2300) in a 3-deep folder hierarchy.

System is:
Windows 10 Home, version 1803
i7-6700K with Z-170 chipset,
GeForce GTX 1080,
Samsung 950 Pro 256GB NVMe SSD.

When I updated from, (to .9 nd then .10) I just used the in-program update function.

I was about to post a separate message but came across this.

The version is slow. It will come up with “Scrivener not responding”. This is after importing a large test novel.

Each scene i press goes in to “sand timer mode” and so i have now deleted the project and will start again.

I am using a 64 bit laptop - Samsung;

4gb RAM;

Quad core processor 1.4 GHz - AMD.

128gb SSD hard drive.

Good luck with the fixes and look forward to buying the final product.

Thank you.

Hi guys, you are all correct that the new version is loading documents a bit slower than the previous one. We also noticed this. We could not solve this on time for the release as we were concentrated mostly on polishing the page view mode, which was a big effort to get it working properly. We know what is causing the delay and will optimize it for the next release. Hope that the initial delay although noticable will not bother you much until we fix this. It’s quite a bit better, I think, but the delay in loading longer documents is still noticeable.

Up to somewhere around 2000-2500 words in a document, the delay is negligible. More than that, and it becomes noticeable, and it seems to depend on how many long docs are in the project. Not sure why.

I’m seeing delays of perhaps 1/2 to 3/4 of a second to load a long document (5500 words, just now). I think that’s probably acceptable, but, of course, faster would be better.

Glad you have noticed the speed improvements, rwfranz. In some cases we got 5-10 times faster loading times, compared to v2.9.0.10. To speed up the loading time further, I am afraid you will have to speed up your machine. :wink:

My main PC is Core i7-6700 (3.4GHz), 16Gb of DDR4 RAM, Samsung SSD, NVidia RTX 2070. As I would expect, Beta 11 really flies.

My 3-year-old laptop is a Core M-5Y10c @ 0.80 GHz, 8Gb RAM, Crucial SSD, Intel HD graphics 5300, Beta 11 performance is perfectly acceptable (but obviously, not as fast)

So, congratulations to the developers; major improvement!

UPDATED (12/12/18). Having used Beta 10 a bit more, I’m a bit less impressed. Again, on the PC it’s fine, but on the laptop I’m getting “Scrivener is not responding” messages quite often. Especially when clicking on the title of a document in the binder or search results list; takes a very long time before the document opens.

I’m running an AMD 1600x with 16GB of memory and multiple HDs.

I’m okay with load times at the moment. Much faster than it used to be.

Have in mind that if you click a document title, which loads all sub-documents in Scrivenings or Outliner mode, the load delay will be proportional to the amount and size of all documents and sub-documents that need to be loaded. If you have a project, which causes “Scrivener not responding”, please email it to “tiho at literatureand latte.com” with steps to reproduce the issue and I will be happy to have a look at it, guys.

Dear tiho_d – I could send you the project if you wish, but it opens eventually (and quickly on my faster computer), so I don’t think the problem is with the project file – it’s simply that (in Beta 11 at least), Scrivener seems to require a pretty powerful PC to respond quickly.

Indeed your laptop CPU spec above at 0.80 GHz is a typo, I hope or not? Any 3 year old laptop CPU including the M series should be faster than 0.8 GHz I believe :slight_smile:.
When comparing Scrivener v1.9 and v3 Beta 11 performance, it should be the same or even faster in favor of v3 Beta 11. Obviously loading huge documents or multiple documents at a time on a slow computer will always show noticeable delays. If you spot any significant Scrivener delays, without any explanation, please let us know, JJE. Providing a reproducible example always helps a lot.

Well, only a minor typo: it’s 900MHz Intel Core M3-6Y30 (dual-core, 4MB cache, 2.2GHz with Turbo Boost). Obviously a long way from state-of-the art, but Scrivener 1.9 runs perfectly; 3.0 is a lot slower.

Obviously, 3.0 has more features, etc., but as a 64-bit app I would not expect it to be massively slower, yet it clearly is on identical hardware. (Also, I would have thought that the storage hardware would be a factor, and I’ve just upgraded its SSD to a Crucial MX500, which has improved performance for other apps.)

Perhaps the minimum specs for Scrivener are (in effect) just going up – as they do for 99% of applications?

I will keep testing and if the problem seems to be more than the elderly hardware, I will post again (with a sample file).

Thanks for your feedback, JJE!

The comparison tests I have seen between 32/64 bit writing application in general does not show a major speed improvement indeed. The biggest benefit of the 64 bit architecture is for big data manipulation algorithms. Scrivener with its relatively small data files will not benefit dramatically from a 64 bit architecture. If you have the time, I would also advice you to try installing the 32-bit of Scrivener Beta 11, use it for a few days and post your personal comparison and experience between the 32 and 64 bit versions of Scrivener. I am personally curious to see, whether you will spot any significant difference on every day bases.

I have a test project with 400 small documents in it. Each one contains 4 lines of text.

No Style 1234567890 Code Block 1234567890 No Style 1234567890 Heading 2 1234567890
With the styles named in the line applied.

In the Binder, using Ctrl-A to “select all” takes over a minute to finish selecting.

There’s only 4400 words. Why does it take so long?

Because loading and laying out 400 documents in Scrivenings mode takes a long time.