Re: [O] How to improve Org startup time?

[Sebastien Vauban]

Hi Achim,

Achim Gratz wrote:
> Sebastien Vauban writes:
>> These are the means over a couple of tests. But the maximum variance (over
>> that small number of tests) is only about 0.04 s -- in powered mode.
>
> File operations on Windows _are_ slow to start with and since a virus
> scanner is more or less required these days, opening a file is getting
> slower yet.

You may be right, but I guess that I'm not alone using Windows 8, so my
performance observations must be shared by others as well. It may even be
worse for some who have more Org files, and a less powerful computer.

So, I'm trying to think what could be done to split the full Org load time
(loading the packages, loading the Org agenda files, scanning them, computing
an agenda view, etc.) into smaller chunks, that the user would experience
depending on his current actions.

For example, why do all the Org agenda files have to be loaded when I'm simply
opening a plain common (I mean: not part of the agenda) Org file?

I don't know if that's possible (or maybe it's already done so), but the
opposite question could make sense: why would have Org agenda buffers to be
fully fontified when the only useful information for building an agenda view
is the "time" information the entries contain (deadline, scheduled,
timestamp).

Hence, my initial request for information:

>> I would like to have:
>>
>> - the minimal Org config loaded when opening any .org file; IOW, certainly
>>   not the agenda files!
>>
>> - all files in `org-agenda-files' when calling any agenda view (C-c a ...)
>>
>> - the current clocked file when resume Org's clock mechanism.
>>
>> I'm ready to look at where to cut branches of the Org tree, if that does
>> make sense to you. Does it?

on which I had no comment.

Best regards,
  Seb

--
Sebastien Vauban