https://bugs.kde.org/show_bug.cgi?id=409587
Matthieu Gallien <matthieu_gall...@yahoo.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
--- Comment #1 from Matthieu Gallien <matthieu_gall...@yahoo.fr> ---
(In reply to Cory F Cohen from comment #0)
> After starting Elisa, I get the following message many thousands of times:
>
> inotify_add_watch(/home/cory/Music/[Artist]/[Album]/[Track].mp3) failed: (No
> space left on device)
>
> My music collection is ~14,000 songs. I'm concerned that the scanning
> approach adopted by Elisa may not be scaling well. For example, the
> "Scanning" message remains on my Elisa window for several minutes, my system
> works fairly hard after starting Elisa, and when running Elisa both it and
> baloo_file consume ~258GiB of virtual RAM (the resident set is much smaller,
> but the behavior is still unusual).
>
> If my scaling concerns are unfounded, please just consider this a report of
> inotify_add_watch() behavior.
>
> STEPS TO REPRODUCE: Start Elisa with a music collection of ~14,000 songs.
> OBSERVED RESULT: The issues listed above.
> EXPECTED RESULT: A quicker/leaner startup and execution without errors.
> SOFTWARE/OS VERSIONS: Kubuntu 19.04, Elisa version 0.4.80 (built from source)
I wanted for a very long time to avoid allowing the user to deactivate checking
deleted files at start. In the end, I will include that alongside the Elisa KCM
redesign. That should allow you to choose between very few activity at start
and quite some. Using Baloo is helping also reduce this and it should also be
possible to improve this use case specifically (I have to check).
The virtual size of baloo and elisa comes from the way the baloo database works
and is really nothing to care about.
--
You are receiving this mail because:
You are watching all bug changes.
