On Mon, Feb 23, 2015 at 11:49 AM, <[email protected]> wrote:
> ??? > Thanks for these questions. Their answers are important. Happily, there seems to be no significant performance difference between @file and @clean. > > 3. A minor advantage: @file makes Leo files smaller. *Leo stores the >> entire @clean *tree* in the .leo file*, but only stores the top-level >> @file *node* in the .leo file. >> >> Does this mean to keep all the files of an entire project in *one* Leo > file? > Yes. > Did you try this on Leo itself, having some hundreds of thousands of lines > in one Leo file? > No, because we aren't going to use @clean for Leo. I tried it on a significant project: pylint. Loading a single .leo is fast, regardless of size. I compared loading the entire project with @file vs. @edit, without significant difference. > What about lazy loading of files and memory usage? > Leo reads external files to determine whether they have been changed. That much is fast. Recreating changed outlines is slower, but happens infrequently. In short, you could say that Leo "lazily" loads @clean trees because the outline only changes if the external file has changed. In practice, everything is fast enough. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
