[frameworks-baloo] [Bug 427344] Ability to configure (higher) number of indexing workers
https://bugs.kde.org/show_bug.cgi?id=427344 --- Comment #3 from philipp.l.kl...@web.de --- It shouldn't be limited I/O wise: My system is on a Samsung SSD 970 EVO Plus 2TB with the following specs: sequential read 3500MB/s, sequential write: 3300MB/s (SLC cached 1750MB/s TLC), IOPS 4K (read/write): 620k/560k. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 427344] Ability to configure (higher) number of indexing workers
https://bugs.kde.org/show_bug.cgi?id=427344 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 427344] Ability to configure (higher) number of indexing workers
https://bugs.kde.org/show_bug.cgi?id=427344 --- Comment #2 from Christoph Feck --- Are you sure on your system the limit isn't the I/O? Using I/O from multiple threads concurrently could even degrade the performance. Also, I don't think the underlying database handles updates from concurrently running threads. It is a simple mmap'ed file, not a SQL database managed by a database server. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 427344] Ability to configure (higher) number of indexing workers
https://bugs.kde.org/show_bug.cgi?id=427344 Nate Graham changed: What|Removed |Added Summary|[Feature Request] Ability |Ability to configure |to configure (higher) |(higher) number of indexing |number of indexing workers |workers Severity|normal |wishlist --- Comment #1 from Nate Graham --- I think this has to be the first request in history for Baloo to use *more* resources. :) -- You are receiving this mail because: You are watching all bug changes.
