Summary: | MYSQL : re-read metadata from images is very slow | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Michael Holtermann <linux> |
Component: | Database-Mysql | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles, swatilodha27 |
Priority: | NOR | ||
Version: | 2.7.0 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.1.0 | |
Attachments: | MySQL Global Status and System Variables |
Description
Michael Holtermann
2012-07-15 10:41:55 UTC
> top shows 84% CPU at mysqld and 35% at digikam, and 3% of MEM, both. iotop > shows nothing. This would indicate the db side as bottleneck, but can be misleading. It will be quite difficult to benchmark, there are two processes involved and at both ends CPU or harddisk I/O can be limiting. > > I guess the meta data reading is done by single kio_digikamtags? I see these > kind of process starting, living for ~6 seconds, and dying. No, this is just updating the tags counter. Scanning is done in a thread of the main process. Hello Marcel, thank you for your reply. I'm running mysql-workbench in parallel, but I'm affraid I'm far away from able to understand the values :-/ I'll attach the status and system variables, assuming that there is something hidden inside... Kind regards, Michael Created attachment 72538 [details]
MySQL Global Status and System Variables
This file still valid using last digiKam 5.0.0 ? Gilles Caulier Sorry, don't know, I'm on Fedora 23 with Digikam 4.14, currently. I guess it's a rare use case that did not gain much attraction, so I think it's fair to close this ticket. |