A behavioral question for graphs:
I am working on my research article vault (84000+) articles for which I refined the article (Markdown file) extraction.
This extraction start form an HTML-file which is queried from the internet.
The article has a title (#-notation), a date and time (##-notation) followed by the article body and keywords (in a ###-heading) with double brackets ([[) and (]] of course).
The global graph takes some time to generate (which is more than normal) - not complaining about that at all.
Suppose I am working on the [[Core banking systems]] theme for which I am selecting ‘dot’ in the graph which automatically creates a Core banking systems.md which is fine. Generating the local graph for this term caught my attention.
It’s now ‘regenerating’ every x-seconds (4-5) for some minutes now…
Seems in the background backlinks are searched and ‘added’ to the graph which causes the ‘regeneration’.
I have the impression that the global graph has this behaviour too.
It starts showing thing rather quick (which is fine for the visual aspect). When zooming out a lot of research articles are ‘around’ the core of the graph (visuals not connected yet). Also there you see ‘regeneration’ by set intervals (4-5 seconds approx.).
I have the impression that after a while this stops but my impression is that the graphing module ‘hangs’.
While writing the articles Obsidian found another 20-ish more backlinks for ‘Core banking systems’, the local graph is still not finished.
Anyone a clue for what is going on?
Would Obsidian work ‘faster’ if I generate the md.file (Core banking systems) in this case with all the forward links to the files?
P.S. Obsidian still generating the local graph. 1046 backlinks now and growing…
I did write a little Python-script to generate the md.file… with between [] the filename of the files that contain the search term (in this case “Core banking systems”)…
When opening the file Core banking systems.md the Linked Mentions ‘Quickly’ grow to 1500-ish mentions and than slow down to add backlinks at the rate the Graph refreshes.
When I close the file (now at 2000-ish backlinks) and reopen it again, the ‘Quick’ behavior goes until 2000-ish files and then slows down again.
So it’s clear this is a caching thing.
Perhaps this ‘triggers’ something for the coders?
Important Hopefully the caching can still be used when closing Obsidian and reopening it again?
Otherwise this would be a big blow for people using Obsidian to do research on big vaults (as I am testing right now).