[digiKam-users] digikam file operations slowed down by baloo_file

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[digiKam-users] digikam file operations slowed down by baloo_file

Bugzilla from martin.tlustos@gmail.com

Hello, everyone

 

I have a question concerning how to set up digikam and baloo so that they don't interfere negatively.

 

Right now, when I want to change the geolocation of a bunch of pictures (our camera doesn't have gps), the process takes a long time because baloo_file kicks in and indexes every change (I have digikam set to write metadata into the image files).

 

My question: is there a way to make file operations go faster? I have several possible szenarios in mind, like:

 

Exclude my images directory/subdirectories from indexing in baloo and activate the option to integrate with baloo in metadata/baloo.

deactivate to write metadata into the files and activate baloo integration in options/metadata/baloo (doesn't feel right, though)

 

Any other ideas? Should I exclude the image directory/subdirectory from indexing with baloo? I should be able to find images within digikam easily, right?

 

Thank you for any help.

 

Regards,

 

Martin

Reply | Threaded
Open this post in threaded view
|

Re: digikam file operations slowed down by baloo_file

digikam-2
On Wed, 25 Mar 2020 17:17:47 +0100
Martin Tlustos <[hidden email]> wrote:

> I have a question concerning how to set up digikam and baloo so
> that they don't interfere negatively.

I'm also on KDE. I have disabled baloo by removing it from
/etc/xdg/autostart

Baloo slows down everything, not just DK.

Instead, I use locate which is part of mlocate and remove it from the
systemd startup with "sudo systemctl mask updatedb" and "sudo systemctl
mask updatedb.timer"

Then whenever I need indexing with new stuff, I run "sudo updatedb"
and search with "locate -i <string>".

--
sknahT

vyS
Reply | Threaded
Open this post in threaded view
|

Re: digikam file operations slowed down by baloo_file

Gilles Caulier-4
Hi,

Baloo is the first KDE service that i remove immediately when i
install a fresh Plasma desktop. This service, even if it can be
interesting for end users to register all the kind of
documents/information, work badly and overload computer for nothing.

Sound like this kind of Plasma feature is technically badly designed
and not fianlized.

Just mu feedback as developper.

Regards

Gilles Caulier

Le mer. 25 mars 2020 à 12:35, <[hidden email]> a écrit :

>
> On Wed, 25 Mar 2020 17:17:47 +0100
> Martin Tlustos <[hidden email]> wrote:
>
> > I have a question concerning how to set up digikam and baloo so
> > that they don't interfere negatively.
>
> I'm also on KDE. I have disabled baloo by removing it from
> /etc/xdg/autostart
>
> Baloo slows down everything, not just DK.
>
> Instead, I use locate which is part of mlocate and remove it from the
> systemd startup with "sudo systemctl mask updatedb" and "sudo systemctl
> mask updatedb.timer"
>
> Then whenever I need indexing with new stuff, I run "sudo updatedb"
> and search with "locate -i <string>".
>
> --
> sknahT
>
> vyS