https://bugs.kde.org/show_bug.cgi?id=404057
Martin Steigerwald <mar...@lichtvoll.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
--- Comment #4 from Martin Steigerwald <mar...@lichtvoll.de> ---
Thanks, Kai for confirming this issue. I can also confirm that I was not able
to stop any of this reliably via balooctl stop / suspend, whatever… just
killing Baloo process (with SIGTERM was enough) helped.
Let's not discuss possible solutions in order to keep the report concise, I'd
say, and first let the developer have a say. I believe there is a bug
somewhere, as I did not see this excessive behavior with earlier version. Baloo
has often been a resource hog, but not in this cross dimension. I am not
positive that high VSZ would have a big influence, so I'd focus on RSS/PSS
usage. Also IMHO Baloo should not need to resort to CGroup limits – IMHO there
is a bug here and I'd first see about addressing it and then whether anything
else is needed. No need to discuss any of that either. Let's just provide the
developer with what we found, the facts. (I know it can be tempting to provide
further guidance. I am holding Linux performance analysis & tuning trainings,
since almost a decade.)
--
You are receiving this mail because:
You are watching all bug changes.
