[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2022-11-30 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=356357 Nate Graham changed: What|Removed |Added Component|Baloo File Daemon |general -- You are receiving this mail because:

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2021-12-08 Thread Micah Shennum
https://bugs.kde.org/show_bug.cgi?id=356357 Micah Shennum changed: What|Removed |Added CC||jimt...@gmail.com -- You are receiving this

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2021-08-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=356357 --- Comment #15 from tagwer...@innerjoin.org --- Is this still an issue ... ? ... To the extent that it can be pinned down to syncing writes to the index? I think there are still things to look at - for example batching up the initial indexing

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2021-08-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=356357 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org -- You are

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2021-02-16 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=356357 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2019-10-12 Thread Martin Steigerwald
https://bugs.kde.org/show_bug.cgi?id=356357 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de -- You are receiving

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2019-10-08 Thread Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=356357 Kai Krakow changed: What|Removed |Added See Also||https://bugs.kde.org/show_b |

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2019-09-29 Thread Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=356357 Kai Krakow changed: What|Removed |Added CC||k...@kaishome.de --- Comment #14 from Kai Krakow

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2019-06-11 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=356357 Nate Graham changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2019-05-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=356357 Nate Graham changed: What|Removed |Added CC||mou...@mail.com --- Comment #13 from Nate Graham

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2019-03-01 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=356357 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2019-01-07 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=356357 soredake changed: What|Removed |Added CC||fds...@krutt.org -- You are receiving this mail

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2018-12-01 Thread Stefan Brüns
https://bugs.kde.org/show_bug.cgi?id=356357 --- Comment #12 from Stefan Brüns --- Eventually the data has to be flushed to disk. The flushing has to be done in a specific order, to guarantee the on-disk data is consistent. You can of course delay the flush, but then you are just shifting the

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2018-12-01 Thread Feng
https://bugs.kde.org/show_bug.cgi?id=356357 Feng changed: What|Removed |Added CC||wang_f...@live.com --- Comment #11 from Feng --- (In

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2018-11-26 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=356357 Jack changed: What|Removed |Added CC||ostroffjh@users.sourceforge |

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2018-11-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=356357 Nate Graham changed: What|Removed |Added CC||igor.pobo...@gmail.com, |

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2018-11-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=356357 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b |

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2017-01-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=356357 --- Comment #9 from k...@web.de --- (In reply to Riku Voipio from comment #8) > (In reply to kdeu from comment #7) > > Are there any experiences whith using LMDB and NOSYNC? > > Personally I've happily used that with patch attached since filing this

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2017-01-03 Thread Riku Voipio
https://bugs.kde.org/show_bug.cgi?id=356357 --- Comment #8 from Riku Voipio --- (In reply to kdeu from comment #7) > Are there any experiences whith using LMDB and NOSYNC? Personally I've happily used that with patch attached since filing this bug - except for a handful of

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2017-01-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=356357 --- Comment #7 from k...@web.de --- > I think it would better to work on detecting and recovering corruption. > MDB_NOSYNC Don't flush system buffers to disk > when committing a transaction. This optimization > means a system crash can corrupt the

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2017-01-03 Thread Riku Voipio
https://bugs.kde.org/show_bug.cgi?id=356357 --- Comment #6 from Riku Voipio --- (In reply to kdeu from comment #5) > https://linux.die.net/man/1/ionice > Baloo's priority is set to Idle, which means it should not cause "abusive" > disk activity. ionice is being used, and it does

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2017-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=356357 k...@web.de changed: What|Removed |Added CC||k...@web.de --- Comment #5 from k...@web.de --- >

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2016-10-14 Thread Idonotexist via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356357 Idonotexist changed: What|Removed |Added CC||obila...@yahoo.com ---

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2016-07-04 Thread Vishesh Handa via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356357 Vishesh Handa changed: What|Removed |Added Assignee|m...@vhanda.in|pinak.ah...@gmail.com --

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

2016-03-11 Thread Alexander Potashev via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356357 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com