https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #51 from Kai Krakow ---
(In reply to tagwerk19 from comment #50)
> (In reply to Kai Krakow from comment #49)
>
> Thank you for the insights. That's a lot more to think about...
You're welcome.
> What we had previously, of BTRFS
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #50 from tagwer...@innerjoin.org ---
(In reply to Kai Krakow from comment #49)
Thank you for the insights. That's a lot more to think about...
I'm not sure I'd worry if Baloo releases memory slowly, provided it releases
it. I'm pretty
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #49 from Kai Krakow ---
(In reply to tagwerk19 from comment #47)
> That said, I've not noticed the percentages behaving differently than a
> defined amount of memory (so, I think a "MemoryHigh=25%" on a 2GB system
> acts the same as a
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #48 from tagwer...@innerjoin.org ---
(In reply to Martin Steigerwald from comment #0)
> 3. If you like to kick it beyond any sanity:
>- have it go at the results of git clone
> https://github.com/danielmiessler/SecLists.git
>- here
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #47 from tagwer...@innerjoin.org ---
(In reply to Kai Krakow from comment #46)
> ... Just my 2 cents, no need to re-open ...
Thank you!
My experience is empirical, I tested out various combinations to see how they
behaved. Means, of course,
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #46 from Kai Krakow ---
(In reply to tagwerk19 from comment #45)
> Yes, there's been a handful of bug reports where I've "blamed" the 512M
> limit.
>
> I tentatively recommend "MemoryHigh=25%". I don't suppose many people run on
> systems
https://bugs.kde.org/show_bug.cgi?id=404057
tagwer...@innerjoin.org changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #44 from Kai Krakow ---
(In reply to tagwerk19 from comment #43)
> I think the dust has probably settled here after:
> https://invent.kde.org/frameworks/baloo/-/merge_requests/131
> and cherrypicked for KF5
>
https://bugs.kde.org/show_bug.cgi?id=404057
soredake changed:
What|Removed |Added
CC|katyaberezy...@gmail.com|
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=404057
tagwer...@innerjoin.org changed:
What|Removed |Added
Status|CONFIRMED |NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=404057
Dennis Schridde changed:
What|Removed |Added
Latest Commit||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=404057
Dennis Schridde changed:
What|Removed |Added
CC||devuran...@gmx.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=404057
euphonis...@outlook.com changed:
What|Removed |Added
CC||euphonis...@outlook.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=404057
Moritz Herrmann changed:
What|Removed |Added
CC||moritzherrmann09+kde.org@gm
https://bugs.kde.org/show_bug.cgi?id=404057
Joachim Wagner changed:
What|Removed |Added
CC||jwag...@computing.dcu.ie
--- Comment #42 from
https://bugs.kde.org/show_bug.cgi?id=404057
Massimiliano L changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=404057
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=404057
tagwer...@innerjoin.org changed:
What|Removed |Added
CC||tagwer...@innerjoin.org
--- Comment
https://bugs.kde.org/show_bug.cgi?id=404057
tagwer...@innerjoin.org changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=404057
soredake changed:
What|Removed |Added
CC||ndrzj1...@relay.firefox.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=404057
gwar...@gmail.com changed:
What|Removed |Added
CC||gwar...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #40 from Kai Krakow ---
Further research confirms: btrfs has unstable device ids because it exposes
subvolumes as virtual block devices without their own device node in /dev.
Thus, device id numbers are allocated dynamically at runtime from
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #39 from Martin Steigerwald ---
Good morning Kai. Overnight I think I got your idea about UUID->CounterID
mapping table. Sounds like an approach that can work. About… the several
databases thing… I get the disadvantages you mention. Of
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #38 from Kai Krakow ---
(In reply to Martin Steigerwald from comment #35)
> I like the idea to use one DB per filesystem. This way you can save the
> complete filesystem UUID and/or other identifying information *once* and use
> the full 64
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #37 from Martin Steigerwald ---
It is probably too late for me or I am not into programming enough at the
moment, to fully understand what you propose. :) May be something to bring to
the suitable Phabricator tasks, maybe
Overhaul Baloo
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #36 from Kai Krakow ---
Oh, nice... Sometimes it helps to talk about a few things.
I could think of the following solution:
Add another UUID->CounterID mapping table to the database, that is easy to
achieve. Everytime we encounter a new
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #35 from Martin Steigerwald ---
I like the idea to use one DB per filesystem. This way you can save the
complete filesystem UUID and/or other identifying information *once* and use
the full 64 bit for the inode number thing.
--
You are
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #34 from Martin Steigerwald ---
I would not worry all that much about redoing the database for a format change.
In the end what we have now that it re-indexes anyway. And yes, I have a multi
device BTRFS. Actually a BTRFS RAID 1.
I wonder
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #33 from Kai Krakow ---
Also, LMDB is totally the wrong tool when using 32-bit systems because your
index cannot grow beyond a certain size before crashing baloo.
I'm not sure if 32-bit systems are still a thing - but if they are, the
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #32 from Kai Krakow ---
(In reply to Martin Steigerwald from comment #30)
> I believe this bug is at
> least about two or three independent issues, but as you told, let's have it
> about the re-indexing files thing. I bet getting rid of
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #31 from Kai Krakow ---
As far as I understand from researching the discussions in phabricator, this
problem won't be easy to fix as it is baked into the design decision that
defined the database scheme.
Based on the fact that the DocId
https://bugs.kde.org/show_bug.cgi?id=404057
Martin Steigerwald changed:
What|Removed |Added
Summary|Uses an insane amount of|Uses an insane amount of
32 matches
Mail list logo
