Let me add a couple of clarifying notes.
- Obsidian already uses some form of parallel processing/asynchronous processing in several of its components.
3.The thread you linked was made in response to your bug report has nothing to do with multi-core processing.
The problem, as I tried to explain in the other thread, is that you use huge lists.
To improve performance, Obsidian dynamically removes the blocks of texts that are not currently displayed on the screen. We do not do that for lists. Doing that for lists is hard.
For example, the level of indentation of what is on the screen depends on the part of the list that comes before it. Therefore, the part of the list that is not currently in view cannot be simply removed (from the HTML).
Another option is to optimize the rendering of extra large (HTML) documents but that is in the hands on chrome developers.