https://bugs.kde.org/show_bug.cgi?id=437754
--- Comment #3 from tagwer...@innerjoin.org ---
(In reply to Martin Steigerwald from comment #2)
> % balooctl indexSize
> File Size: 8,12 GiB
> Used: 77,17 MiB
There's some analysis/discussion/confusion about the percentages here:
https://bugs.kde.org/show_bug.cgi?id=354636#c10
I think the "used" sizes are believable. I have copied/compressed a test index
with
mdb_copy -n -c index index.new
(from lmdb-utils) and this changes "indexSize" details from:
File Size: 2,28 GiB
Used: 18,99 MiB
PostingDB: 4,89 MiB 25.735 %
PositionDB: 4,92 MiB 25.921 %
DocTerms: 2,47 MiB 13.001 %
DocFilenameTerms: 1,70 MiB 8.969 %
DocXattrTerms: 4,00 KiB 0.021 %
IdTree: 240,00 KiB 1.234 %
IdFileName: 1,94 MiB 10.204 %
DocTime: 1,29 MiB 6.809 %
DocData: 1,53 MiB 8.044 %
ContentIndexingDB: 0 B 0.000 %
FailedIdsDB: 0 B 0.000 %
MTimeDB: 12,00 KiB 0.062 %
to:
File Size: 19,37 MiB
Used: 18,99 MiB
PostingDB: 4,89 MiB 25.735 %
PositionDB: 4,92 MiB 25.921 %
DocTerms: 2,47 MiB 13.001 %
DocFilenameTerms: 1,70 MiB 8.969 %
DocXattrTerms: 4,00 KiB 0.021 %
IdTree: 240,00 KiB 1.234 %
IdFileName: 1,94 MiB 10.204 %
DocTime: 1,29 MiB 6.809 %
DocData: 1,53 MiB 8.044 %
ContentIndexingDB: 0 B 0.000 %
FailedIdsDB: 0 B 0.000 %
MTimeDB: 12,00 KiB 0.062 %
Which points at loads of "empty space" created during the deletions/status.
This is on ext4, after having created 50000 files and deleted 20000. I will try
the same on BTRFS
Whether this helps any...?
--
You are receiving this mail because:
You are watching all bug changes.
