I wonder if anyone knows about the order in which the plugins are loaded. Some plugins are reported as loaded or indexing in the console (CTRL+SHIFT+I), but I don’t remember having been able to draw a conclusion on the prioritization by Obsidian to load this or that plugin first.
- By the way, I mentioned this in this post.
I tried out the Lazy Plugins plugin from that thread and was looking on how things develop.
I’ve found that my DataView indexing finished in about 1/3rd of the time I clocked before (50-60secs to 15-25secs on a larger vault).
Possibly, in the Lazy Plugin-less default loading fashion, two (indexing?) processes (internal + external or two or even more external?) were running side by side, making the Dataview indexing slower.
So to answer your question, it is possible that some kink was untangled in the process but maybe you forgot to turn some plugin back on, even… Who knows.
One thing’s for sure. There are some rules to go by here and some caveats to how Obsidian is being used and whether you are a power user (with many notes, not to mention with a low-end older computer), etc.
What did pain me from 3 weeks ago is that how did I go from an almost perfectly working setup (I had a slight lag on typing but no major issues) to one that was virtually unusable.
So I said goodbye to some plugins (Remember Cursor Position, Editing Toolbar, Excalidraw, and I could go on with the list), started using Lazy Plugins to seperate loading slots of resource-demanding, indexing plugins, kept enabled Commander only (with Status Bar icons) instead of Editing Toolbar, and started using Source Mode in all files (optionally flicking on Live Preview on demand), etc.
- In my case, simply typing in 2-3 lines sent the RAM usage of the main process so high the laptop went into a near-unresponsive state, which is when data loss can even happen. Typing itself was lagging, which makes the use of the app, well, not so enjoyable.
So going back to a low amount of external plugins kind of setup is a good idea and one can even get lucky with courses of action that one cannot really explain (yet).
I recommend trying out the Lazy Plugins method as well, or another method mentioned in this thread.