In theory I suspect that there may be a maximum technical size for a Scrivener project, but I don’t know what it is. (There have been discussions of this question in these forums in the past in which - if I remember correctly - L&L people participated, so a search should reveal them.)
In practice (as opposed to theory) with some other writing tools, saving to disk poses a bottleneck which can slow down use and provide a practical limit to size. Scrivener is different from most. You’ll notice that in my first sentence I used the word “project”, not “file”. You may not be aware that a Scrivener project can be composed of hundreds or even thousands of files. This helps to protect the project from corruption, and it also means that only a few of the files in the project are loaded into RAM memory at any one time. So in practical (as opposed to theoretical) terms, as far as I know you should be unlikely to run into a limit when the project is being saved to disk in normal use.
There are two exceptions - that I know of - to this guidance. One is that if you have fewer, larger documents (and so files), that will (logically) slow up saving to disk. For the same project size, more, smaller documents are better, from this point of view.
The second is backing up. Backups are the only times when a complete project is saved to disk in one go. If, say, you have set your project to “backup on project close” (in Scrivener > Preferences > Backup), you may find that your 3 GB takes a while to be backed up, and your project takes a while to close.
A final thought: you are taking a risk by putting all your eggs in such a large basket. Although Scrivener has been built to help safeguard projects against corruption, no digital tool is 100 per cent proof against it. In this respect, two or more smaller projects would be safer than a single very large one.
Thanks a lot for your detailed answer and view, Hugh.
Your thoughts about the RAM usage was what I was looking for. The thoughts about the saving time/bottle neck with large files was already clear. So, Scrivener files are organized like any other folder storage, one can say (I think) - that helps a lot.
I got all my single files separately as copies on an external drive additionally, so I’m save. But to have them one click away within Scrivener makes it much more comfortable…
Also thanks Katherine, OCR wouldn’t match with my fast running scrawl, but would be an good advice when I could discipline myself to write slower. But then my thoughts would be boiled away before I could write them down.
I will challenge Scrivener on the file size to figure out how it can match with my special workflow…
My largest project has roughly 3500 files and 700 MB. I find that this project takes significantly longer to save and load than my other projects and sometimes will say “not responding” and need to sit for a minute to sort itself out. My computer is fairly up to date (2016) and plays video games without an issue, so I’m sure this is Scrivener’s capacity that is causing the delay.
To Scrivener’s credit – it successfully accepted an import of 3000 files at once! It took it around an hour to import.
~ Raederle www.Raederle.com
Having 3500 files is going to slow down any indexing operation, since you’ll have 3500 open/read/close operations. A project with the same overall size but fewer component files would probably be zippier.