-
-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance drop in 2.0.0 release #1800
Comments
I have done a git bisect start
Reverting d7593a2 does fix the problem. |
I've asked for advice in Discord. No replies yet. |
@ilandikov - For your information... Sorry to be the bearer of this news, and really sorry that I did not spot it in testing the fix for #1732. This is the source of the big slow-down in editing in 2.0.0 that I mentioned... @gypsyav - We will need to try and find a fix for the canvas bug that doesn't hit the Tasks rendering efficiency. Otherwise, sadly, I think I may need to do a bug-fix release in the next day or two that reverts the slow-down. |
Oh wow. Well the fix was inspired by blacksmithgu/obsidian-dataview#1661 In the meantime it is definitely worth it to revert the bug fix. |
I had the same thought, and let the dataview author know in Discord that it would be worth checking if it does. The Dataview code is a lot more optimised for speed than Tasks, so there could be something else there that prevents wasted redraws, for example. |
Please check that this issue hasn't been reported before.
Expected Behavior
The following all work correctly in Tasks 1.25.0
Scenario 1
Scenario 2
Current behaviour
The behavior in Tasks 2.0.0
Scenario 1
Scenario 2
Steps to reproduce
Tasks 1.25.0
You will see the behaviour described above.
Tasks 2.0.0
Now repeat the above with 2.0.0, and you will see the same number of 'task has changed' messages - but a lot more 're-rendering' messages, even for files you have closed.
Which Operating Systems are you using?
Obsidian Version
1.1.16
Tasks Plugin Version
2.0.0
Checks
Possible solution
No response
The text was updated successfully, but these errors were encountered: