Skip to content
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

Slow! #35

Open
tsbertalan opened this issue Jan 24, 2022 · 2 comments
Open

Slow! #35

tsbertalan opened this issue Jan 24, 2022 · 2 comments

Comments

@tsbertalan
Copy link

Either toggling a checkbox with the keyboard shortcut, or opening the modal with the n/N buttom in the bottom bar are both very slow (like, 30s).

(After opening the modal, clicking a checkbox, and then clicking "OK", the file is modified within four seconds--still slow, but ok.)

This is in a Foam workspace with 2643 notes and about 500,000 files overall.

@PKief
Copy link
Owner

PKief commented Jan 26, 2022

I am sorry that it is so slow in your case. I haven't used the extension with so many files in a workspace yet, so I haven't experienced it so slow. For the creation of the checkboxes I mostly use the VS Code API. I may check it out when I get a chance to see if I can improve the performance. Thanks for bringing this to my attention.

@tsbertalan
Copy link
Author

I tried uninstalling and reinstalling today; same problem. To provide a little more detail, it seems to work normally if I open the sub-directory containing my test file (which contains 658 markdown files and 3246 files in general), but not in the previous folder (parent of the parent of the folder with the test file, now with 2742 markdown files and 366300 files overall).

It does eventually toggle the checkbox, but it's unusably slow.

I also tried disabling "Date When Checked", "Italic When Checked", and "Strike Through When Checked", though those, like the whole extension, shouldn't really care whether the containing folder has 1 or 1000000 (markdown() files. No dice. The extension is doing something with the whole workspace that it really shouldn't be, to have this scaling issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants