No it won't be fixed in the kernel, it's a really old bug that has been opened and closed for years. The desktop distributions should choose a scheduler that behaves better with a UI (BFQ really helps).
But system responsiveness is exceptionally bad with baloo even when compared with other heavy IO loads like backup, find, sysbench and file transfers. Baloo should restrain itself even if takes longer to index the files. On 25 April 2014 03:52, Pavel Volkov <sai...@lists.xtsubasa.org> wrote: > On Friday, April 25, 2014 5:35:47 AM MSK, Nikos Chantziaras wrote: > >> The problem is not baloo itself, but the I/O scheduler of the Linux >> kernel. >> > > Does it mean it's not going to be fixed in near future neither in Baloo > nor in kernel? > Patching kernel isn't what should be expected of an average user. > > ___________________________________________________ > This message is from the kde mailing list. > Account management: https://mail.kde.org/mailman/listinfo/kde. > Archives: http://lists.kde.org/. > More info: http://www.kde.org/faq.html. >
___________________________________________________ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
