@ericjpaint @EyeOdin @kacart could you please share the content of Help → Show Krita log for bug reports? It will be long so preferably on something like pastebin.com, it will show your paths (including username on your system) so if you want to make it more private, make sure to make it unlisted and to self-destruct in two weeks or so. Or change them with Find and Replace if you know how.
What I will be looking for is statement Database is up to date. It will show up only if the database is not being created from scratch. So absence of this text (in the first few lines of the log for every day) will mean that Krita does try to create it from scratch every time. (I hope I’ll remember to add another log line for the “creating database from scratch” event…)
For everyone with this issue, please also give me this information:
- do you have plenty of
resourcecache.sqlite.n~(wherenis a number) and if yes, how many (roughly)? - look at the creation date of
resourcecache.sqlite, then close Krita and open again, and look at the creation date again, is it different (and set to just a moment ago)? - if you create your own custom tag, close Krita and reopen, does it still exist?
- system, and the path to the resources (is it default or not) and if you’re on Windows, then if you use Windows Store package or some other (Steam or Epic Store or just from the website)
- how many resources and tags do you have? I mean besides the default ones.
- If you know how, it would be awesome if you could backup your resource folder and start Krita a few times with a newly created one, and see if it’s faster.
If it’s not the database recreating but just the database queries taking so long, we have a shimmer of hope in a form of this MR: Draft: Improve performance of query in KisTagResourceModel (!1302) · Merge requests · Graphics / Krita · GitLab - it makes quite an important query (which takes longer if you have plenty of resources and plenty of tags) even up to 4x faster. And I’m working on other performance improvements, too. But we gotta first check what is really going on here 