Mostly for SEARCH efficiency

Posts: 144
Joined: Sat Oct 25, 2014 12:59 am
Platform: Windows

Tue May 12, 2020 4:36 pm Post

1) It seems that from another post, larger files are more quickly handled than smaller? (The file open/close operations are mostly an issue for indexing, not actual searching?)

2) Does the depth of severally-branched branches from the trunk of the tree (thrice or more) have a relatively negative impact vs for an un-twigged branch for the textbase/docbase? (Do subdocuments 'count' as branches?)

3) Does a tree trunk's main branching (25+) have a relatively negative impact vs none beyond DRAFT and RESEARCH?

(Overall, ~ 25k files in a 430 MB project.)

- Windows 10 64b; i7 7700, 2T main storage, 32G RAM;
Scrivener 1.9.16

User avatar
Posts: 6970
Joined: Fri Feb 02, 2007 5:22 pm
Platform: Mac

Tue May 12, 2020 4:41 pm Post

Scrivener is not intended to be a dedicated database program. If you are asking these kinds of questions, your use case is probably outside of Scrivener's intended scope.

Scrivener creates a separate search index as you work, and searches that index rather than crawling the Binder directly. So the exact structure of the Binder is less relevant than the overall number of words in the project.

Scrivener Support Team