I don't understand.

What problem is this trying to solve?

Tasks does already automatically refresh the view.

If a query with many tasks is fixed and permanently displayed in the sidebar while additional tasks are added in notes, obsidian freezes completely. The cursor remains fixed for several seconds before the next letters that have already been written appear and Obsidian freezes again. This behavior is intensified if the display of the task query output has been adjusted with custom CSS. This behavior is so massively annoying that I am already considering leaving Obsidian again, as it is not possible to work productively this way. The only alternative would be not to leave the query output permanently open in the sidebar, which is not an option for me.

Thank you for the extra info - the context is clear now.

Yes, I agree that the performance in this area needs improving.

Please run the Obsidian Show debug info command and paste the result in here, in a fenced code block. Thank you.

Thank you. Very helpful.

I see you are using displaying searches in tabs:

Do those other tabs display tasks search results too?

In my experience, the plugins that offer Tabs support generally render all their tabs all the time - which also has a bad effect on performance.

The other tabs also show task queries. I have already investigated whether this could be related and have built a small dashboard with only a single task query and without using the tab plugin. Then I thought it might be due to the Dataview Calendar I was using and also removed it from the alternative dashboard. Although the latency then improved somewhat, it could not be completely eliminated by all these measures.

This behavior will of course strongly depend on the respective user, the number of tasks, user-defined CSS and so on. Therefore, I thought that an implementation of View Refresh identical to Dataview could offer all affected users an option to prevent this annoying problem on their own (if required).

This issue

Now I feel like there is enough information to understand the value of the feature - I have renamed it so the intention is clear.

This behavior is so massively annoying that I am already considering leaving Obsidian again

I understand.

If you do decide to stop using the Tasks plugin, please kindly let me know.

It's very frustrating to do work on things in one's free time, only to find that the requestor no longer needs the functionality.

Recent work

I have recently spent some time trying to make Tasks "debounce" rendering, so it renders less often.

Unfortunately my initial attempts resulted in code blocks being stuck at "initialising tasks...". So more work is required.

Related requests

These are all the existing requests and ideas to improve the performance/responsiveness of Tasks:

• is:issue state:open label:"scope: performance issues"

You can see that I have labelled several already as "priority: high".

I have not yet decided in what order to work on them, but do intend to start work on this area fairly soon, once current in-progress work is released.