-
-
Notifications
You must be signed in to change notification settings - Fork 402
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 regression on auto-complete #1417
Comments
I don't think it has anything to directly with Previously |
Oooh, that's interesting. It does match a lot of tags from a quick look through the csv file. One obviously workaround would be to edit the csv file, but I'd rather avoid that if possible 😅 |
I think sorting and cutting off the csv is not a bad idea in general (not by hand obviously) - the tags with low use-count won't work anyway. Not sure if that throws out enough of the Don't have a great idea how to fix it in code. Could start auto-complete only at the 4th character, but that makes it less useful. Or special case the |
Commit 1c5e832, which was created created to address #1294 seems to have caused a performance regression on auto-completion (I have confirmed with a git bisect).
I don't fully understand what is going wrong here, but here's the completion file I am using:
fluffyrock-unbound-tag-completion.csv
Replication steps:
fluffyrock-unbound-tag-completion
completion file in the settings.by
and press space.It will then take some time to process things:
krita_2024-11-18_12-49-59.mp4
Locally reverting this commit seems to have fixed the issue - I wonder if the
lstrip
function could be much more computationally intensive than expected?The text was updated successfully, but these errors were encountered: