https://bugs.kde.org/show_bug.cgi?id=490484
Maik Qualmann <metzping...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|REPORTED |RESOLVED
Version Fixed In| |8.5.0
--- Comment #79 from Maik Qualmann <metzping...@gmail.com> ---
The multiple blocked database accesses in a row come from your many CPU
threads, they all come across a database that is still busy at the same time
and have to resend their request. But that doesn't really take much time. Using
WAL mode optimizes the SQLite database even more.
I wrote before that you write the metadata twice if you write the metadata
manually beforehand and then use lazy synchronization. In that case, your
manual writing of the metadata is unnecessary. We can think about deleting the
waiting image IDs from the lazy synchronization waiting list if a manual
writing of the metadata was forced.
Thanks for the logs and feedback to solve the problem.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
