Re: Digikam-users Digest, Vol 243, Issue 17
Jan Steinman <[email protected]>
| Newsgroups | gmane.comp.kde.digikam.user |
|---|---|
| Message-ID | <[email protected]> |
> I would imagine moving the db external to the machine running DK would come with a performance penalty due to the introduction of network latency. It depends. MariadDB on an SSD across CAT-V (rather than WiFi) could easily perform better than using SQLite locally on a spinning disk. In my experience, MySQL (and clones) perform better than SQLite when there's a large number of records. > Date: Wed, 20 Aug 2025 13:50:57 +0200 > From: Thomas <[email protected]> > > Hi Nick, > > > Thanks for sharing your experience! > > A couple of questions: > > > 1: How quickly does the homebrew package tend to be updated when a new > release of DK is publised? > > 2: You mention that you moved from a local db to external Mariadb. May I > ask what were the major drivers for this change? I would imagine moving > the db external to the machine running DK would come with a performance > penalty due to the introduction of network latency. > > BR > > Thomas > > > On 2025-08-20 13.17, Nick Seward wrote: >> Hi Thomas, >> >> I’ve been using the homebrew install of DK for over 3 years now. >> I run it on Apple silicon, an M2 mini. I had it with the local SQL db to start and now I have it connecting to an external MariaDB database. >> No issues or loss of features that I can see. >> >> It may not be officially managed by the DK team but it’s always up to date. >> >> Of course you can validate this by comparing the hash of the homebrew version with the downloadable pkg. >> >> Nick > >