https://bugs.kde.org/show_bug.cgi?id=499170
--- Comment #7 from korwin <korwin+kde....@proton.me> --- (It's a pity that there is no way to supplement my previous message here instead of adding a new one. Also, please forgive me for describing my experience with tags here, given that the topic primarily concerns file processing after a single read versus multiple reads of the same file for different processing operations. However, I cannot delete my previous message, nor leave it without the promised addition.) After three days of testing version 8.7.0 on Windows 10, I can say that it is noticeably more pleasant when working with tags. According to my observations, if there are no more than ~8-10 thousand files in the queue, the application freezes completely for the duration of the task for only a few hours. If the number of files in the queue is more than ~10 thousand, the application stops responding forever (at least for 15 hours). At least such irreversible freezes occur only 2-3 times a day, which is bearable. After a couple of hours of waiting, I kill the application processes, launch it again and repeat the last tasks in smaller portions. This is much better than it was a month ago! I would have guessed that it was less about application optimization and more about the move from SQLite to (embedded) MySQL, but https://bugs.kde.org/show_bug.cgi?id=431951#c16 claimed that with about half a million files, SQLite actually unexpectedly gives better performance. Sorry, I didn't give any specifics. -- You are receiving this mail because: You are watching all bug changes.
