Proposal for Multi-Core Processing to Boost Obsidian's Efficiency

[Sam12]

Recently, I’ve devised a method to indirectly enable Obsidian to utilize multiple cores. Although this approach won’t work for canvases and lists, it allows different windows to use separate CPUs. The method involves using mklink.

1. Create Multiple Vaults: Copy multiple .obsidian folders and create new folders to establish new Obsidian vaults. By linking notes across vaults, they can share the same folder.
2. Assign CPUs via Task Manager: Use the Task Manager to assign different CPUs to each vault, enabling different windows to operate on separate CPUs.

For more details, you can refer to this forum post.

Are there any drawbacks to using mklink /j for linking notes across vaults?

Thank you both for your replies. I tried using Obsidian URI, but it seems it cannot achieve the functionality similar to ![]. Additionally, I found that neither method can effectively handle situations where there are attachments in the file. The only issue I have discovered so far is that if it is a canvas file, the images in the canvas file cannot be displayed correctly because it does not use the shortest path. I think this method can effectively solve cross-vault referencing. Advantages: …

In this post, I enabled two sub-vaults to be accessed by the main vault. Note that this doesn’t mean creating a new .obsidian folder under the main vault. Instead, it involves using mklink /j to link the folders that need to be shared.
However, this method could have a couple of drawbacks. First, updating configurations requires synchronization, which can be very time-consuming. Second, if multiple windows edit the same file, it may lead to sudden content loss.