https://bugs.kde.org/show_bug.cgi?id=338402
Daniel Vrátil <dvra...@redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |CONFIRMED CC| |dvra...@redhat.com Severity|grave |normal Ever confirmed|0 |1 --- Comment #2 from Daniel Vrátil <dvra...@redhat.com> --- The large folder works very efficiently on common filesystem (ext, btrfs, ...), since we are just making use of the internal hashtree implementation of the filesystem. We always know full name of the file we want, so we never list content of the directory, just directly ask for a specific file, which filesystems are generally very efficient at dealing with. However we already had a similar report for some remote FS implementation that had a hard limit on maximum amount of files in directory, so I'm inclined to implement one or two levels of folders indirection. However as the most common filesystem in use on desktops work just fine, I'm not assigning this top priority now. It's definitely something for Frameworks though. To workaround the issue, you can configure a higher threshold for storing payload in external files, i.e. Akonadi will store more data in the database and put only really large payloads on filesystem. To do so, open ~/.config/akonadi/akonadiserverrc and in [General] section, add SizeThreshold=16384 This will store externally only payloads larger than 16KB. The default is 4KB. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs