Hi
Last year I discussed here about the convenience of disable "auto searching" just in single search when the user type any letter or if some search was done previously and the user open the "Search" tab. On large databases it hangs DK. In DK 6.1 I was presuming it was changed, but it is not. You implemented a hidden and not very intuitive way to disable the "autosearch". I needed to search in this forum to find a way to do it (http://digikam.1695700.n4.nabble.com/digiKam-users-dk6b3-searches-td4707224.html#a4707235). So, please, to avoid headaches for users with large databases, could you change the option to "DK configuration, Others, Search" or even a button next to the search cell with "Search with enter" enabled by default, or even simply a "Search" button. Any way that let user choose when the search must begin. Thank you -- Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html |
On Fri, 28 Jun 2019 03:43:05 -0500 (CDT)
Rafael Linux <[hidden email]> wrote: > Last year I discussed here about the convenience of disable "auto > searching" just in single search when the user type any letter or > if some search was done previously and the user open the "Search" > tab. On large databases it hangs DK. In DK 6.1 I was presuming it > was changed, but it is not. You implemented a hidden and not very > intuitive way to disable the "autosearch". I needed to search in > this forum to find a way to do it > (http://digikam.1695700.n4.nabble.com/digiKam-users-dk6b3-searches-td4707224.html#a4707235). It's not just large datasets, even medium one. The problem is the thumbnails. DK is retrieving the thumbnails for the images that qualify for the "as is" search. > So, please, to avoid headaches for users with large databases, > could you change the option to "DK configuration, Others, Search" > or even a button next to the search cell with "Search with enter" > enabled by default, or even simply a "Search" button. Any way that > let user choose when the search must begin. +++++1 It would make DK much more responsive. The other problem is that DK remember the last search and tries to execute it when I enter the search tab. * If after the search I close DK. * If the last search was a very large dataset, something like almost almost all the images. Starting DK will "take forever" because not only it's checking for the new images, but it's also executing the search from the last time (which I don't need anymore). * DK doesn't like having the search interrupted. More often than not, DK would crash if I interrupt the search. * I've had to learn to live with the very slow starts because I exited DK after a search. Now I try to remember to switch back to albums before exiting. -- sknahT vyS |
How big are your databases? I'm managing ~100000 pictures and I haven't had
any problems with slowdowns in searches. Only in the timeline view it takes a while when several years are selected. -- Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html |
On Fri, 28 Jun 2019 10:42:04 -0500 (CDT)
woenx <[hidden email]> wrote: > How big are your databases? I'm managing ~100000 pictures and I > haven't had any problems with slowdowns in searches. Only in the > timeline view it takes a while when several years are selected. For me it, it's the search. I never use the timeline digikam version 6.1.0 Images: GIF: 5 JPG: 864 PNG: 16 PSD: 49 RAW-CR2: 30830 RAW-DNG: 8489 RAW-PEF: 1765 RAW-RAF: 6454 TIFF: 306 XCF: 8 total: 48786 : Total Items: 48786 Albums: 305 Tags: 148 : Database backend: QSQLITE Database Path: /drive-b/photos/ > df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 5.9G 0 5.9G 0% /dev tmpfs 5.9G 0 5.9G 0% /dev/shm tmpfs 5.9G 9.6M 5.9G 1% /run tmpfs 5.9G 0 5.9G 0% /sys/fs/cgroup /dev/sda2 322G 8.9G 297G 3% / /dev/sdb1 2.7T 1.6T 1.1T 61% /drive-b <<<<<<<<<< /dev/sda3 2.4T 320G 2.0T 14% /home tmpfs 1.2G 16K 1.2G 1% /run/user/1000 Drives: HDD Total Size: 6001.2GB (34.4% used) ID-1: /dev/sda model: WDC_WD30EFRX size: 3000.6GB ID-2: /dev/sdb model: WDC_WD30EFRX size: 3000.6GB > ls -alF /drive-b/photos/ (abbreviated) total 2621104 -rw-r--r-- 1 froggy users 95563776 Jun 28 08:47 digikam4.db drwxr-xr-x 3 froggy users 4096 Nov 7 2018 .mysql.digikam/ -rw-r--r-- 1 froggy users 36864 Jun 28 08:47 recognition.db -rw-r--r-- 1 froggy users 24576 Jun 28 08:47 similarity.db -rw-r--r-- 1 froggy users 2588114944 Jun 28 08:48 thumbnails-digikam.db -- sknahT vyS |
In reply to this post by woenx
+300K with MySQL and SSD and, as digikam-2 wrote, is the search. A large
database with commentaries and plenty of metadata for more than 85% of images, logically will drown CPU if the searching begins just even without typing nothing and then you just begin to type while CPU is busy. Then DK will stop respond, freezing for many time (even 5 minutes or more) till it shows the searching results. -- Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html |
Free forum by Nabble | Edit this page |