https://bugs.kde.org/show_bug.cgi?id=356357
Bug ID: 356357
Summary: Continous index flushing with fdatasync degrades
interactive performance
Product: Baloo
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: m...@vhanda.in
Reporter: nc...@kos.to
CC: pinak.ah...@gmail.com
While baloo is indexing, the KDE UI becomes periodically unresponsive. While
stracing the baloo_file_extractor, it is apparent the unresponsiveness happens
when fdatasync() is called:
59872
pwrite(16,
"D\16\6\0\0\0\0\0\t\25\4\0\303\2\0\0\1\10\0\0\26\1\0\1\1\10\0\0E\1\0\1"...,
2895872, 1625571328) = 2895872
pwrite(16,
"\377w\6\0\0\0\0\0\240\376\4\0\254\3\0\0\1\10\0\0\26\1\0\1\1\241P\1\10\0\0
"..., 3850240, 1736437760) = 3850240
fdatasync(16, ...
It would be better to use MDB_NOSYNC and regenerate the index in the extremely
unlikely event of database corruption.
--
You are receiving this mail because:
You are watching all bug changes.
