Dgk 5.5 very slow start
Locked
12
12
 
|
Hello,
Installed 5.5 in Kubuntu VM.
Reading db in the start take now too long. More than 15 min.
I can see only uses 1.7 gb of memory out of available 5.8
Any solution?
antoni
|
|
|
Hello, I have never had such issue before. Was the process any faster on another system (what system?) ? Are you using mysql or sqlite? How many items are in the database? Where the database file is located (HDD?, its speed?, SSD ?) Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: antoni olivella <[hidden email]> Date: 2017-03-27 7:58 AM (GMT-07:00) To: [hidden email] Subject: Dgk 5.5 very slow start Hello,
Installed 5.5 in Kubuntu VM.
Reading db in the start take now too long. More than 15 min.
I can see only uses 1.7 gb of memory out of available 5.8
Any solution?
antoni
|
|
|
Hi, i have the very same issue. DigiKam 5.5 with mysql external Pictures are on a NAS drive Picasa has no problems with this drive. There are ~ 220000 items Digikam startup takes ~ 15 to 30 minutes Von: Digikam-users [mailto:[hidden email]]
Im Auftrag von Andrey Goreev Hello, I have never had such issue before. Was the process any faster on another system (what system?) ? Are you using mysql or sqlite? How many items are in the database? Where the database file is located (HDD?, its speed?, SSD ?) Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: antoni olivella <[hidden email]>
Date: 2017-03-27 7:58 AM (GMT-07:00)
To: [hidden email] Subject: Dgk 5.5 very slow start Hello, Installed 5.5 in Kubuntu VM. Reading db in the start take now too long. More than 15 min. I can see only uses 1.7 gb of memory out of available 5.8 Any solution? antoni |
|
|
In reply to this post by antoni olivella
If you are on Linux please run digiKam in terminal and watch what is showing in it on startup. I suspect digiKam is still creating thumbnails. It takes long time for a large collection especially if you have many video files. Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: "Dumelle, Timo (E+K)" <[hidden email]> Date: 2017-04-03 2:18 AM (GMT-07:00) To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> Subject: AW: Dgk 5.5 very slow start Hi, i have the very same issue. DigiKam 5.5 with mysql external Pictures are on a NAS drive Picasa has no problems with this drive. There are ~ 220000 items Digikam startup takes ~ 15 to 30 minutes Von: Digikam-users [mailto:[hidden email]]
Im Auftrag von Andrey Goreev Hello, I have never had such issue before. Was the process any faster on another system (what system?) ? Are you using mysql or sqlite? How many items are in the database? Where the database file is located (HDD?, its speed?, SSD ?) Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: antoni olivella <[hidden email]>
Date: 2017-03-27 7:58 AM (GMT-07:00)
To: [hidden email] Subject: Dgk 5.5 very slow start Hello, Installed 5.5 in Kubuntu VM. Reading db in the start take now too long. More than 15 min. I can see only uses 1.7 gb of memory out of available 5.8 Any solution? antoni |
Re: AW: Dgk 5.5 very slow start
|
|
This can be also something around similarity search. I'm not sure. The debug trace on the console must be informative... Gilles Caulier 2017-04-03 15:37 GMT+02:00 Andrey Goreev <[hidden email]>:
|
|
|
In reply to this post by AndriusWild
Hi,
I've updated my digikam on Saturday to 5.5.0 and the start is on my account @home suddenly very very slow, too. Here @work I've got a very small database and don't see problems. I am using digikam on opensuse tumbleweed, plasma 5. ~/Pictures/meta/digikam4.db (sqlite) is 162MB and located on SSD. Unluckily if I try to read my personalized function key settings digikam crashes, so I've been waiting for digikam to start rather a long time more than once, yesterday. CLI start or even strace -e open -f didn't show anything special in my eyes (but I am willing to upload any debugging information wanted this evening). What type of startup options / strace options would be helpful for debugging in this case? Best wishes, Hella -- [hidden email] http://www.unixwitch.de |
|
|
2017-04-03 16:46 GMT+02:00 Hella Breitkopf <[hidden email]>: Hi, Nothing. the text trace on the console must be enough to discover where application hand. If not, running in to GDB can help. When it hand, just press CTRL+C and enter "bt" to see where you stop the application. This can help. Gilles Caulier |
|
|
It happens for me as well. DK5.5 on Linux Mint with SqLite, about 20K pics. I have attached the terminal listing and indicated the point at which it paused for a few minutes. Mick On 03/04/17 16:25, Gilles Caulier
wrote:
|
TerminalListing (20K) |
|
My output looks very similar to the one of Mick Sulley
with the same "pause" in the sequence. I did try to create a "freshly built" database (migrate) because I was to dumb to find tools>maintenance), which really made digikam4.db smaller (162MB to 66MB), but the pause remains. Next step will be to "maintain" the other databases, too. And than gdb ... -- [hidden email] http://www.unixwitch.de |
|
|
From the trace : digikam.general: Added root album called: "Album" digikam.general: Using 8 CPU core to run threads digikam.general: Action Thread run 1 new jobs digikam.general: Using 8 CPU core to run threads digikam.general: Using 8 CPU core to run threads digikam.general: Action Thread run 1 new jobs digikam.general: Action Thread run 1 new jobs ** Stopped at this point for a few minutes ** digikam.general: Using 8 CPU core to run threads digikam.general: Action Thread run 1 new jobs The pause section is not enough explicit. This can be : - The search completer text field from bottom album tree view which need time to be populated (problem fixed globally in current implementation by Maik). - Virtual album as Similarity which are populated from DB while init. I'm not sure. What's give GDB + CTRL-C + bt while stop point, to see where DK loop in code ? Gilles Caulier 2017-04-04 2:09 GMT+02:00 Hella Breitkopf <[hidden email]>: My output looks very similar to the one of Mick Sulley |
|
|
Hi,
my gdb run with backtrace might be downloaded from: https://foto.unixwitch.de/temp/digikam/gdb-digikam-2017-04-04.txt (as it is to big for this mailinglist). Unluckily I've most of the debugging libraries not installed, if some special or all would be helpfull I'd install them (this evening). Best wishes, Hella -- [hidden email] http://www.unixwitch.de |
|
|
From the trace : #12 0x00007ffff4d46cc2 in QTreeWidgetItem::sortChildren(int, Qt::SortOrder, bool) () from /usr/lib64/libQt5Widgets.so.5 #13 0x00007ffff4d46dcf in ?? () from /usr/lib64/libQt5Widgets.so.5 #14 0x00007ffff4d47ef5 in ?? () from /usr/lib64/libQt5Widgets.so.5 #15 0x00007ffff4d3ee1e in ?? () from /usr/lib64/libQt5Widgets.so.5 #16 0x00007ffff4d40d39 in QTreeWidget::setItemHidden(QTreeWidgetItem const*, bool) () from /usr/lib64/libQt5Widgets.so.5 #17 0x00007ffff76ed785 in ?? () from /usr/lib64/libdigikamgui.so.5.5.0 #18 0x00007ffff76edbd0 in ?? () from /usr/lib64/libdigikamgui.so.5.5.0 #19 0x00007ffff76eb3d0 in ?? () from /usr/lib64/libdigikamgui.so.5.5.0 #20 0x00007ffff76f1bcc in ?? () from /usr/lib64/libdigikamgui.so.5.5.0 #21 0x00007ffff3dc1709 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #22 0x00007ffff76d5482 in Digikam::AlbumManager::signalAlbumAdded(Digikam::Album*) () from /usr/lib64/libdigikamgui.so.5.5.0 #23 0x00007ffff76c2fa5 in Digikam::AlbumManager::scanSAlbums() () from /usr/lib64/libdigikamgui.so.5.5.0 #24 0x00007ffff76c8e49 in Digikam::AlbumManager::refresh() () from /usr/lib64/libdigikamgui.so.5.5.0 #25 0x00007ffff76c918f in Digikam::AlbumManager::startScan() () from /usr/lib64/libdigikamgui.so.5.5.0 #26 0x00007ffff74be6c3 in Digikam::DigikamApp::DigikamApp() () Album manager populate the treeview for search album. This can be similarity stuff... So this is what i suspected. I see some commits since 5.5.0 release to optimize this behavior. I'm not sure if this fix really the problem, but i recommend to test 5.6.0 appimage that i build as pre release sunday evening. Gilles Caulier 2017-04-04 10:03 GMT+02:00 Hella Breitkopf <[hidden email]>: Hi, |
|
|
TL;DR: digikam 5.6.0 appimage shows the same problem.
Long: I did download the 5.6.0 appimage variant and startet it. Unluckily there seems to be the same error... [..] digikam.dimg: variant: QVariant(Digikam::LensFunIface::DevicePtr, ) digikam.dimg: dev: AEE :: AEE DV :: 6 digikam.dimg: Search for camera "" - "" ==> false digikam.dimg: Search for lens "" ==> false digikam.dimg: updating data digikam.dimg: updating data digikam.general: Using 4 CPU core to run threads digikam.general: new search text settings: "" : hasResult = false , validRows = 0 QFSFileEngine::open: No file name specified digikam.general: Added root album called: "foto" digikam.general: Using 4 CPU core to run threads digikam.general: Action Thread run 1 new jobs digikam.general: Using 4 CPU core to run threads digikam.general: Using 4 CPU core to run threads digikam.general: Action Thread run 1 new jobs digikam.general: Action Thread run 1 new jobs ^C Program received signal SIGINT, Interrupt. 0x00007ffff769b5fa in waitpid () from /lib64/libc.so.6 (gdb) bt #0 0x00007ffff769b5fa in waitpid () from /lib64/libc.so.6 #1 0x0000000000492850 in wait_for () #2 0x000000000047f9b7 in execute_command_internal () #3 0x0000000000480c11 in execute_command () #4 0x0000000000480280 in execute_command_internal () #5 0x0000000000480c11 in execute_command () #6 0x0000000000480280 in execute_command_internal () #7 0x0000000000480c11 in execute_command () #8 0x0000000000480280 in execute_command_internal () #9 0x0000000000480c11 in execute_command () #10 0x0000000000474db9 in reader_loop () #11 0x0000000000474a0b in main () -- [hidden email] http://www.unixwitch.de |
|
|
Same thing.
Digikam needs the same time booting up -----Ursprüngliche Nachricht----- Von: Digikam-users [mailto:[hidden email]] Im Auftrag von Hella Breitkopf Gesendet: Dienstag, 4. April 2017 21:36 An: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> Betreff: Re: Dgk 5.5 very slow start TL;DR: digikam 5.6.0 appimage shows the same problem. Long: I did download the 5.6.0 appimage variant and startet it. Unluckily there seems to be the same error... [..] digikam.dimg: variant: QVariant(Digikam::LensFunIface::DevicePtr, ) digikam.dimg: dev: AEE :: AEE DV :: 6 digikam.dimg: Search for camera "" - "" ==> false digikam.dimg: Search for lens "" ==> false digikam.dimg: updating data digikam.dimg: updating data digikam.general: Using 4 CPU core to run threads digikam.general: new search text settings: "" : hasResult = false , validRows = 0 QFSFileEngine::open: No file name specified digikam.general: Added root album called: "foto" digikam.general: Using 4 CPU core to run threads digikam.general: Action Thread run 1 new jobs digikam.general: Using 4 CPU core to run threads digikam.general: Using 4 CPU core to run threads digikam.general: Action Thread run 1 new jobs digikam.general: Action Thread run 1 new jobs ^C Program received signal SIGINT, Interrupt. 0x00007ffff769b5fa in waitpid () from /lib64/libc.so.6 (gdb) bt #0 0x00007ffff769b5fa in waitpid () from /lib64/libc.so.6 #1 0x0000000000492850 in wait_for () #2 0x000000000047f9b7 in execute_command_internal () #3 0x0000000000480c11 in execute_command () #4 0x0000000000480280 in execute_command_internal () #5 0x0000000000480c11 in execute_command () #6 0x0000000000480280 in execute_command_internal () #7 0x0000000000480c11 in execute_command () #8 0x0000000000480280 in execute_command_internal () #9 0x0000000000480c11 in execute_command () #10 0x0000000000474db9 in reader_loop () #11 0x0000000000474a0b in main () -- [hidden email] http://www.unixwitch.de |
|
|
There are few commits since Sunday, done by Maik and Mario. I will rebuild AppImage bundles tomorrow to see if problem occur again. Gilles 2017-04-05 8:16 GMT+02:00 Dumelle, Timo (E+K) <[hidden email]>: Same thing. |
|
|
yes, It's fully reproducible here : digikam.general: Using 8 CPU core to run threads digikam.general: new search text settings: "" : hasResult = false , validRows = 0 QFSFileEngine::open: No file name specified digikam.geoiface: ---- digikam.general: Added root album called: "GILLES" ^C Program received signal SIGINT, Interrupt. Digikam::Album::next (this=0x39f1320) at /b/dktemp/digikam-master/core/libs/album/album.cpp:97 97 /b/dktemp/digikam-master/core/libs/album/album.cpp: No such file or directory. Missing separate debuginfos, use: debuginfo-install glibc-2.20-24.mga5.x86_64 lib64dbus1_3-1.8.20-1.mga5.x86_64 lib64expat1-2.1.0-9.3.mga5.x86_64 lib64fontconfig1-2.11.1-4.1.mga5.x86_64 lib64glib2.0_0-2.42.1-2.1.mga5.x86_64 lib64gpg-error0-1.13-3.mga5.x86_64 lib64ice6-1.0.9-3.mga5.x86_64 lib64openal1-1.16.0-4.mga5.x86_64 lib64pcre1-8.38-1.mga5.x86_64 lib64sm6-1.2.2-4.mga5.x86_64 lib64udev1-217-11.2.mga5.x86_64 lib64usb1.0_0-1.0.19-9.mga5.x86_64 lib64uuid1-2.25.2-3.5.mga5.x86_64 lib64x11_6-1.6.3-1.mga5.x86_64 lib64xcb1-1.11.1-1.mga5.x86_64 lib64xcursor1-1.1.14-5.mga5.x86_64 lib64xdmcp6-1.1.1-7.mga5.x86_64 lib64zlib1-1.2.8-7.1.mga5.x86_64 libgcc1-4.9.2-4.1.mga5.x86_64 libstdc++6-4.9.2-4.1.mga5.x86_64 (gdb) bt #0 Digikam::Album::next (this=0x39f1320) at /b/dktemp/digikam-master/core/libs/album/album.cpp:97 #1 0x00007ffff77035d0 in findNthChild (this=<optimized out>, n=2398, parent=<optimized out>) at /b/dktemp/digikam-master/core/libs/models/abstractalbummodelpriv.h:70 #2 Digikam::AbstractAlbumModel::index (this=0xb3a070, row=2398, column=<optimized out>, parent=...) at /b/dktemp/digikam-master/core/libs/models/abstractalbummodel.cpp:236 #3 0x00007ffff770aabd in Digikam::AlbumFilterModel::filterAcceptsRow (this=0x12b5860, source_row=2398, source_parent=...) at /b/dktemp/digikam-master/core/libs/models/albumfiltermodel.cpp:362 #4 0x000000348925d12f in ?? () from /tmp/.mount_ttEEDt/usr/lib/libQt5Core.so.5 #5 0x000000348925dee9 in ?? () from /tmp/.mount_ttEEDt/usr/lib/libQt5Core.so.5 #6 0x00000034892af846 in QMetaObject::activate(QObject*, int, int, void**) () from /tmp/.mount_ttEEDt/usr/lib/libQt5Core.so.5 #7 0x0000003489322ea4 in QAbstractItemModel::rowsInserted(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) () from /tmp/.mount_ttEEDt/usr/lib/libQt5Core.so.5 #8 0x000000348923512d in QAbstractItemModel::endInsertRows() () from /tmp/.mount_ttEEDt/usr/lib/libQt5Core.so.5 #9 0x00007ffff7703ab3 in Digikam::AbstractAlbumModel::slotAlbumAdded (this=0xb3a070, album=<optimized out>) at /b/dktemp/digikam-master/core/libs/models/abstractalbummodel.cpp:459 #10 0x00000034892af846 in QMetaObject::activate(QObject*, int, int, void**) () from /tmp/.mount_ttEEDt/usr/lib/libQt5Core.so.5 #11 0x00007ffff77546a2 in Digikam::AlbumManager::signalAlbumAdded (this=this@entry=0x7ffff7ddbfb0 <_ZZN7Digikam12_GLOBAL__N_113Q_QGS_creator13innerFunctionEvE6holder>, _t1=_t1@entry=0x12296c00) at /b/dktemp/digikam-master/build/core/libs/album/moc_albummanager.cpp:583 #12 0x00007ffff7742e24 in Digikam::AlbumManager::scanSAlbums (this=this@entry=0x7ffff7ddbfb0 <_ZZN7Digikam12_GLOBAL__N_113Q_QGS_creator13innerFunctionEvE6holder>) at /b/dktemp/digikam-master/core/libs/album/albummanager.cpp:1790 #13 0x00007ffff7748479 in Digikam::AlbumManager::refresh (this=this@entry=0x7ffff7ddbfb0 <_ZZN7Digikam12_GLOBAL__N_113Q_QGS_creator13innerFunctionEvE6holder>) at /b/dktemp/digikam-master/core/libs/album/albummanager.cpp:1263 #14 0x00007ffff7748774 in Digikam::AlbumManager::startScan (this=0x7ffff7ddbfb0 <_ZZN7Digikam12_GLOBAL__N_113Q_QGS_creator13innerFunctionEvE6holder>) at /b/dktemp/digikam-master/core/libs/album/albummanager.cpp:1071 #15 0x00007ffff7550704 in Digikam::DigikamApp::DigikamApp (this=0x650690, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /b/dktemp/digikam-master/core/app/main/digikamapp.cpp:262 #16 0x0000000000405888 in main (argc=1, argv=<optimized out>) at /b/dktemp/digikam-master/core/app/main/main.cpp:236 (gdb) Investigations is under progress... Please wait... Gilles Caulier 2017-04-05 10:10 GMT+02:00 Gilles Caulier <[hidden email]>:
|
|
|
The problem must be fixed with new AppImage bundles just built. Files are under upload to GDrive and will be available in few hours : Gilles Caulier 2017-04-05 11:46 GMT+02:00 Gilles Caulier <[hidden email]>:
|
|
|
Unluckily I see the problem also with digikam-5.6.0-01-x86-64.appimage
(gdb output snippet): digikam.general: Added root album called: "foto" digikam.general: Using 4 CPU core to run threads digikam.general: Action Thread run 1 new jobs digikam.general: Using 4 CPU core to run threads digikam.general: Using 4 CPU core to run threads digikam.general: Action Thread run 1 new jobs digikam.general: Action Thread run 1 new jobs ^C Program received signal SIGINT, Interrupt. 0x00007ffff769b5fa in waitpid () from /lib64/libc.so.6 (gdb) bt #0 0x00007ffff769b5fa in waitpid () from /lib64/libc.so.6 #1 0x0000000000492850 in wait_for () #2 0x000000000047f9b7 in execute_command_internal () #3 0x0000000000480c11 in execute_command () #4 0x0000000000480280 in execute_command_internal () #5 0x0000000000480c11 in execute_command () #6 0x0000000000480280 in execute_command_internal () #7 0x0000000000480c11 in execute_command () #8 0x0000000000480280 in execute_command_internal () #9 0x0000000000480c11 in execute_command () #10 0x0000000000474db9 in reader_loop () #11 0x0000000000474a0b in main () On Wed, Apr 5, 2017 at 7:15 PM, Gilles Caulier <[hidden email]> wrote: > The problem must be fixed with new AppImage bundles just built. Files are > under upload to GDrive and will be available in few hours : > > https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM > > Gilles Caulier -- [hidden email] http://www.unixwitch.de |
|
|
In reply to this post by Gilles Caulier-4
I have the same problem. 5.4 opened all right, 5.5 does it very slowly. The console output:
[..] digikam.dimg: updating data digikam.general: Using 4 CPU core to run threads digikam.general: new search text settings: "" : hasResult = false , validRows = 0 QFSFileEngine::open: No file name specified digikam.geoiface: ---- digikam.general: Added root album called: "2017" digikam.general: Added root album called: "JVK" >>>>> Here is an about 4 minutes long wait <<<<< digikam.general: Using 4 CPU core to run threads digikam.general: Action Thread run 1 new jobs digikam.geoiface: ---- digikam.geoiface: ---- digikam.general: Using 4 CPU core to run threads digikam.general: Action Thread run 1 new jobs digikam.geoiface: ---- digikam.general: Cancel Main Thread digikam.geoiface: ---- digikam.general: Using 4 CPU core to run threads digikam.general: Action Thread run 1 new jobs digikam.geoiface: "ROADMAP" digikam.geoiface: ---- digikam.general: Cancel Main Thread [..] JVK album contains about 800 photos. |
|
|
Since on my computer the pause is about 15 - 20 Minutes
(for > 50 000 Pictures) I am motivated to enhance my debugging efforts (as far as I am able to, I am a sysadmin, not a software developer) Would a core-dump help? Best wishes, Hella -- [hidden email] http://www.unixwitch.de |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |