[digiKam-users] DK6b3 hogs CPU
Locked
 
|
DK 6.0 beta 3 dated: 5-Nov.
It really hogs the CPU and everything slows down when flagging. Assign label > pick > pending: alt-2 and depending (on what I don't know) when DK uses between 33% to 81% of the CPU, as per htop. While assign stars is instantaneous. 8-Core model: AMD FX-8350 bits: 64 type: MCP arch: Bulldozer L2 cache: 2048 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 64034 Speed: 1852 MHz min/max: 1400/4000 MHz Core speeds -- sknahT vyS |
|
|
We need more information here : Which kind of database ? Where are located database file ? Where are the collections ? local ? Remote ? What's kind of debug trace do you see on the console while you apply labels ? What's your metadata settings ? Did you use XMP sidecar files ? Do you reproduce the dysfunction for all items in collections or only few one ? As you can see the equation is complex and just a parameter can introduce a dysfunction. Best Gilles Caulier Le mer. 7 nov. 2018 à 06:15, <[hidden email]> a écrit : DK 6.0 beta 3 dated: 5-Nov. |
|
|
On Wed, 7 Nov 2018 09:21:48 +0100
Gilles Caulier <[hidden email]> wrote: > We need more information here : > > Which kind of database ? SQLITE > Where are located database file ? on a second local drive sata3: /dev/sdb1 > Where are the collections ? local ? Remote ? all local to the on the second drive /dev/sdb1 > What's kind of debug trace do you see on the console while you > apply labels ? I don't see any debug. It was running slow so I started HTOP to see if there was something else in the background. > What's your metadata settings ? https://i.imgur.com/rMCLz1j.png and https://i.imgur.com/fdChpz8.png > Did you use XMP sidecar files ? yes > Do you reproduce the dysfunction for all items in collections or > only few one ? all > > As you can see the equation is complex and just a parameter can > introduce a dysfunction. here are the db stats digikam version 6.0.0-beta3 Images: GIF: 4 JPG: 859 PNG: 16 PSD: 45 RAW-CR2: 29902 RAW-DNG: 8443 RAW-PEF: 1764 RAW-RAF: 5836 TIFF: 302 XCF: 6 total: 47177 : Total Items: 47177 Albums: 297 Tags: 145 : Database backend: QSQLITE Database Path: /drive-b/photos/ > > Best > > Gilles Caulier > > Le mer. 7 nov. 2018 à 06:15, <[hidden email]> a écrit : > > > DK 6.0 beta 3 dated: 5-Nov. > > > > It really hogs the CPU and everything slows down when flagging. > > > > Assign label > pick > pending: alt-2 and depending (on what I > > don't know) when DK uses between 33% to 81% of the CPU, as per > > htop. > > > > While assign stars is instantaneous. > > > > 8-Core model: AMD FX-8350 bits: 64 type: MCP arch: Bulldozer > > L2 cache: 2048 KiB > > flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm > > bogomips: 64034 Speed: 1852 MHz min/max: 1400/4000 MHz Core speeds > > > > > > -- > > sknahT > > > > vyS > > -- sknahT vyS |
|
|
On 11/7/18 3:35 PM, [hidden email] wrote:
>> What's kind of debug trace do you see on the console while you >> apply labels ? > > I don't see any debug. It was running slow so I started HTOP to see > if there was something else in the background. To see debug, just launch Digikam in terminal |
|
|
Do I understand correctly that digiKam generates a base load at idle by 33%?
Maik Am Mittwoch, 7. November 2018, 17:15:46 CET schrieb [hidden email]: > On 11/7/18 3:35 PM, [hidden email] wrote: > >> What's kind of debug trace do you see on the console while you > >> apply labels ? > > > > I don't see any debug. It was running slow so I started HTOP to see > > if there was something else in the background. > > To see debug, just launch Digikam in terminal |
|
|
On Wed, 07 Nov 2018 22:01:28 +0100
Maik Qualmann <[hidden email]> wrote: > Do I understand correctly that digiKam generates a base load at > idle by 33%? No. DK uses 33% when flagging with assign label > pick flag: I use alt-2 and alt-3. I have 8 cpus (no hyperthreading). 1 of them goes 100% then it becomes 2 or 3 cpus running around 50% (all according to HTOP) This does NOT happen for the tags, the ratings, the captions... I have started from the command line and I assign a pick flag Digikam::MaintenanceThread::slotThreadFinished: List of Pending Jobs is empty Digikam::adjustedEnvironmentForAppImage: Adjusting environment variables for AppImage bundle Digikam::DNotificationWrapper: Event is dispatched to desktop notifier through DBUS Digikam::adjustedEnvironmentForAppImage: Adjusting environment variables for AppImage bundle Digikam::DNotificationWrapper: Event is dispatched to desktop notifier through DBUS Digikam::ActionThreadBase::cancel: Cancel Main Thread Digikam::ActionThreadBase::cancel: Cancel Main Thread Digikam::ScanController::slotRelaxedScanning: Starting scan! unknown: Parse error in "/home/froggy/.config/menus/applications-merged/xdg-desktop-menu-dummy.menu" , line 1 , col 1 : "unexpected end of file" unknown: Parse error in "/home/froggy/.config/menus/applications-merged/xdg-desktop-menu-dummy.menu" , line 1 , col 1 : "unexpected end of file" unknown: The menu spec file contains a Layout or DefaultLayout tag without the mandatory Merge tag inside. Please fix your file. Digikam::TagsActionMngr::slotAssignFromShortcut: Shortcut value: 2 Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using 8 CPU core to run threads Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using 8 CPU core to run threads Digikam::ActionThreadBase::run: Action Thread run 1 new jobs Digikam::ActionThreadBase::run: Action Thread run 1 new jobs Digikam::ActionThreadBase::slotJobFinished: One job is done Digikam::ActionThreadBase::cancel: Cancel Main Thread Digikam::ActionThreadBase::slotJobFinished: One job is done Digikam::ActionThreadBase::cancel: Cancel Main Thread > > Maik > > Am Mittwoch, 7. November 2018, 17:15:46 CET schrieb > [hidden email]: > > On 11/7/18 3:35 PM, [hidden email] wrote: > > >> What's kind of debug trace do you see on the console while you > > >> apply labels ? > > > > > > I don't see any debug. It was running slow so I started HTOP to > > > see if there was something else in the background. > > > > To see debug, just launch Digikam in terminal > > > > -- sknahT vyS |
|
|
In reply to this post by leoutation
I have added a test debug message, it will be included in the next AppImage. I would like to know if this message goes through in the console even when digiKam is idle and no mouse cursor is moved over the icon view:
digikam.general: ImageCategorizedView::paintEvent() QTime("22:36:29.700") Maik
Am Mittwoch, 7. November 2018, 17:15:46 CET schrieb [hidden email]: > On 11/7/18 3:35 PM, [hidden email] wrote: > >> What's kind of debug trace do you see on the console while you > >> apply labels ? > > > > I don't see any debug. It was running slow so I started HTOP to see > > if there was something else in the background. > > To see debug, just launch Digikam in terminal
|
|
|
Thanks
I'll try when the appimage comes out. On Wed, 07 Nov 2018 22:44:40 +0100 Maik Qualmann <[hidden email]> wrote: > I have added a test debug message, it will be included in the next > AppImage. I would like to know if this message goes through in the > console even when digiKam is idle and no mouse cursor is moved over > the icon view: > > digikam.general: ImageCategorizedView::paintEvent() > QTime("22:36:29.700") > > Maik > > Am Mittwoch, 7. November 2018, 17:15:46 CET schrieb > [hidden email]: > > On 11/7/18 3:35 PM, [hidden email] wrote: > > >> What's kind of debug trace do you see on the console while you > > >> apply labels ? > > > > > > I don't see any debug. It was running slow so I started HTOP to > > > see if there was something else in the background. > > > > To see debug, just launch Digikam in terminal > > -- sknahT vyS |
|
|
I will start new AppImage build tomorrow morning. Gilles Le mer. 7 nov. 2018 à 22:59, <[hidden email]> a écrit : Thanks |
|
|
In reply to this post by digikam-2
This probably has less to do with their problem and comes from https://
bugs.kde.org/show_bug.cgi?id=373839. I want to see if there are constant paint events under other desktop environments, that would be a performance problem. The CPU consumption at the flag set goes with me in the CPU noise and is hardly noticeable when writing only in the DB, the additional writing to the file at 5% (dual core). Maik Am Mittwoch, 7. November 2018, 22:57:51 CET schrieb [hidden email]: > Thanks > > I'll try when the appimage comes out. > > On Wed, 07 Nov 2018 22:44:40 +0100 > > Maik Qualmann <[hidden email]> wrote: > > I have added a test debug message, it will be included in the next > > AppImage. I would like to know if this message goes through in the > > console even when digiKam is idle and no mouse cursor is moved over > > the icon view: > > > > digikam.general: ImageCategorizedView::paintEvent() > > QTime("22:36:29.700") > > > > Maik > > > > Am Mittwoch, 7. November 2018, 17:15:46 CET schrieb > > > > [hidden email]: > > > On 11/7/18 3:35 PM, [hidden email] wrote: > > > >> What's kind of debug trace do you see on the console while you > > > >> apply labels ? > > > > > > > > I don't see any debug. It was running slow so I started HTOP to > > > > see if there was something else in the background. > > > > > > To see debug, just launch Digikam in terminal |
|
|
In reply to this post by Maik Qualmann
On Wed, 07 Nov 2018 22:44:40 +0100
Maik Qualmann <[hidden email]> wrote: > I have added a test debug message, it will be included in the next > AppImage. I would like to know if this message goes through in the > console even when digiKam is idle and no mouse cursor is moved over > the icon view: > > digikam.general: ImageCategorizedView::paintEvent() > QTime("22:36:29.700") > > Maik Yes it comes through, but the time is different, it's my current time: Digikam::ImageCategorizedView::paintEvent: ImageCategorizedView::paintEvent() QTime("08:04:00.180") Digikam::ImageCategorizedView::paintEvent: ImageCategorizedView::paintEvent() QTime("08:04:00.191") > > Am Mittwoch, 7. November 2018, 17:15:46 CET schrieb > [hidden email]: > > On 11/7/18 3:35 PM, [hidden email] wrote: > > >> What's kind of debug trace do you see on the console while you > > >> apply labels ? > > > > > > I don't see any debug. It was running slow so I started HTOP to > > > see if there was something else in the background. > > > > To see debug, just launch Digikam in terminal > > -- sknahT vyS |
|
|
Yes, of course it's always the current time for it to see in the console that
it "goes through". My question is whether it also "runs through" when digiKam is simply idle and the mouse pointer is not moved over the icon view? Maik Am Donnerstag, 8. November 2018, 17:07:11 CET schrieb [hidden email]: > On Wed, 07 Nov 2018 22:44:40 +0100 > > Maik Qualmann <[hidden email]> wrote: > > I have added a test debug message, it will be included in the next > > AppImage. I would like to know if this message goes through in the > > console even when digiKam is idle and no mouse cursor is moved over > > the icon view: > > > > digikam.general: ImageCategorizedView::paintEvent() > > QTime("22:36:29.700") > > > > Maik > > Yes it comes through, but the time is different, it's my current time: > > Digikam::ImageCategorizedView::paintEvent: > ImageCategorizedView::paintEvent() QTime("08:04:00.180") > Digikam::ImageCategorizedView::paintEvent: > ImageCategorizedView::paintEvent() QTime("08:04:00.191") > > Am Mittwoch, 7. November 2018, 17:15:46 CET schrieb > > > > [hidden email]: > > > On 11/7/18 3:35 PM, [hidden email] wrote: > > > >> What's kind of debug trace do you see on the console while you > > > >> apply labels ? > > > > > > > > I don't see any debug. It was running slow so I started HTOP to > > > > see if there was something else in the background. > > > > > > To see debug, just launch Digikam in terminal |
|
|
On Thu, 08 Nov 2018 21:37:14 +0100
Maik Qualmann <[hidden email]> wrote: > Yes, of course it's always the current time for it to see in the > console that it "goes through". My question is whether it also > "runs through" when digiKam is simply idle and the mouse pointer is > not moved over the icon view? No it does NOT. BTW, the newest version of dk6b3 dated 8-Nov feels faster the b1 and b2. Thanks Syv > > Maik > > Am Donnerstag, 8. November 2018, 17:07:11 CET schrieb > [hidden email]: > > On Wed, 07 Nov 2018 22:44:40 +0100 > > > > Maik Qualmann <[hidden email]> wrote: > > > I have added a test debug message, it will be included in the > > > next AppImage. I would like to know if this message goes > > > through in the console even when digiKam is idle and no mouse > > > cursor is moved over the icon view: > > > > > > digikam.general: ImageCategorizedView::paintEvent() > > > QTime("22:36:29.700") > > > > > > Maik > > > > Yes it comes through, but the time is different, it's my current > > time: > > > > Digikam::ImageCategorizedView::paintEvent: > > ImageCategorizedView::paintEvent() QTime("08:04:00.180") > > Digikam::ImageCategorizedView::paintEvent: > > ImageCategorizedView::paintEvent() QTime("08:04:00.191") > > > Am Mittwoch, 7. November 2018, 17:15:46 CET schrieb > > > > > > [hidden email]: > > > > On 11/7/18 3:35 PM, [hidden email] wrote: > > > > >> What's kind of debug trace do you see on the console while > > > > >> you apply labels ? > > > > > > > > > > I don't see any debug. It was running slow so I started > > > > > HTOP to see if there was something else in the background. > > > > > > > > To see debug, just launch Digikam in terminal > > > > -- sknahT vyS |
|
|
[hidden email] wrote:
> > BTW, the newest version of dk6b3 dated 8-Nov feels faster the b1 and > b2. > Where does one find the latest beta? The link on the web site always seems to be one behind the version being discussed here. -- Chris Green · |
|
|
This link is given also in web site, from download page. Gilles Caulier Le ven. 9 nov. 2018 à 10:33, Chris Green <[hidden email]> a écrit : [hidden email] wrote: |
|
|
In reply to this post by Maik Qualmann
Hi,
On db6b3: 10-Nov-2018, fixed. Now it's instantaneous Thanks On Wed, 07 Nov 2018 22:44:40 +0100 Maik Qualmann <[hidden email]> wrote: > I have added a test debug message, it will be included in the next > AppImage. I would like to know if this message goes through in the > console even when digiKam is idle and no mouse cursor is moved over > the icon view: > > digikam.general: ImageCategorizedView::paintEvent() > QTime("22:36:29.700") > > Maik > > Am Mittwoch, 7. November 2018, 17:15:46 CET schrieb > [hidden email]: > > On 11/7/18 3:35 PM, [hidden email] wrote: > > >> What's kind of debug trace do you see on the console while you > > >> apply labels ? > > > > > > I don't see any debug. It was running slow so I started HTOP to > > > see if there was something else in the background. > > > > To see debug, just launch Digikam in terminal > > -- sknahT vyS |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |