The Extended Graph plugin includes performance settings to help maintain smooth operation across different vault sizes and configurations.

Initialization delay

• Set a delay (in milliseconds) before the plugin starts initializing
• Default: 500ms
• Increase this value if you experience initialization issues due to asynchronous loading of other plugins or vault content
• Lower values will make the extended graph features start faster but might cause conflicts with the core plugin initialization

Maximum node limit

• Sets the maximum number of nodes allowed before the plugin automatically disables
• Default: 20 nodes
• When exceeded, the plugin will automatically disable to prevent performance degradation
• Adjust based on your computer's capabilities and selected features

While the default node limit is set conservatively, the plugin has been tested on graphs containing over 400 nodes, with approximately 50% of nodes displaying images. In such large graphs, initial loading may be extended and occasionally require multiple attempts. However, once successfully loaded, the graph maintains stable performance. Your experience may vary depending on your system specifications and graph complexity. A comprehensive performance benchmark is planned to provide more detailed guidance on optimal node limits for different configurations.

Usage recommendations

1. Start conservative

   • Begin with the default settings
   • Gradually adjust based on your system's performance
   • Monitor graph responsiveness when making changes

2. Local vs Global graphs

   • Local graphs typically perform better due to fewer nodes
   • Consider enabling some features only in local graphs, especially for images

3. Dynamic changes

   • Consider disabling the Extended Graph in a graph view while you edit your vault notes. Dynamic changes (editing, moving, deleting, etc.) can cause heavy recomputation.

Example

My biggest vault so far has 609 nodes. I tried to enable as much features as I could to record the plugin at its worse with this number of nodes (I know it's not a lot compared to some vaults with thousands of notes). As you can see, the initialization takes a few seconds but then it runs correctly, just a little bit slower than without the plugin.

And here is how it handles filtering nodes and links: