Bypassing Extended Loading Cache...(After first index)

DISCLAIMER: I HAVE NO CODING EXPERTISE, THIS IS FROM EMPIRICAL TESTING. PLEASE BACKUP BEFORE YOU TRY THIS. TRY AT YOUR OWN RISK

Step 0: Turn off any resource extensive plugin.(I have only 3-4 core plugins and no community plugins for this)

Step 1:
Have your vault fully indexed by obsidian at least once.

Step 2:
Close your vault, don’t have to close your app.

Step 3:
Find your IndexedDB folder
Mac: /Users/Your Username/Library/Application Support/obsidian/IndexedDB

Step 4: Make a new folder with any name. Mine is “backup”.
Step 5: Open your vault.
Step 6: Put the “app_obsidian.md_0.indexeddb.leveldb” folder inside of “backup” folder. This will make obsidian skip “loading cache…” screen.
Step 7: Quickly put the “app_obsidian.md_0.indexeddb.leveldb” back into the “IndexedDB” folder.

----SUCCESS----

Comparison:


VS


Context
I have 150k md files of around 5kb each for a japanese vocabulary network for personal use. The loading cache has always been an issue where I needed to delete the IndexedDB folder to enter the vault and would have to reindex for 5+ minutes to begin usage. So I thought why not try to cheat the system by skipping loading cache then putting index files back to reduce the index time, which works wonderfully.

Some interesting things to note:
The index folder is larger than my entire vault combined.


And here’s an image of the vault before obsidian turned into a gray screen. Probably more than half of the 150k nodes are represented here.

It looks like it’s still a bug. I just happened to leave a few large files in the vault, which caused getting stuck at “Loading cache” forever. From then on the vault was dead, even with the large files removed. Only way to fix it is:

  1. either move it somewhere else (thus, the caching mechanism will not kick in)
  2. delete the IndexedDB folder (@TGPNG above suggest basically the same, just backing up first, and selectively remove the file relevant to your vault)