<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I wanted to give you an additional piece of information: I just had
the same issue again and could test what file is accessed:<br>
The unresponsivness (grey window) occurs while digikam is reading
(sic!) from thumbnails-digikam.db.<br>
<br>
<div class="moz-cite-prefix">On 22/07/16 22:03, Gilles Caulier
wrote:<br>
</div>
<blockquote
cite="mid:CAHFG6sGvQ_XFyS5VqSf-=6Y3dsi4i_rsgQ2BFw+DrXJcafOxkg@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">2016-07-22 21:19 GMT+02:00 Simon Frei
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:freisim93@gmail.com" target="_blank">freisim93@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Thanks for the
information.<br>
We discussed the issue of database location earlier
already. In the meantime I locate the database in ram,
so access is fast (digikam as a whole is a lot faster
now). My issue is not that digikam was slow, it is that
it became completely. unresponsive for no apparent
reason (no performance limit).<br>
For clarification (I have no knowledge of database
programming): Internal mysql uses the same "system" as
sqlite and the recent patches discussed were only
concerning external mysql?<br>
</div>
</blockquote>
<div><br>
</div>
<div>yes there are. sqlite still unchanged.</div>
<div><br>
</div>
<div>Mysql database is more designed to work with huge data,
not sqlite. This is why this kind of DB exists.</div>
<div>Don't forget the low level interface from Qt which is
different slightly different than sqlite.</div>
<div><br>
</div>
<div>Gilles Caulier</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Trying mysql is on
my list, but only after I reorganised my collection. If
sqlite really proves to be unusable with lots of data, I
may switch earlier.
<div>
<div class="h5"><br>
<br>
<div>On 22/07/16 19:38, Gilles Caulier wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">The time latency from gui are done
certainly by sqlite lock because a lots lots
data need to be managed in database.
<div><br>
</div>
<div>Did you store the DB file in a fast device
as a SSD. This improve also the performance
until a limit of course.</div>
<div><br>
</div>
<div>In all case, as you use git/master code,
Mysql must give better results. We will
interested to have a comparison.</div>
<div><br>
</div>
<div>Gilles Caulier</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2016-07-22 19:35
GMT+02:00 Gilles Caulier <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:caulier.gilles@gmail.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:caulier.gilles@gmail.com">caulier.gilles@gmail.com</a></a>></span>:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div dir="ltr">From my experience sqlite
use must be limited to 100Gb of images.
For more, use Mysql. You can use
internal server, no need a remote
server. In this case, it will be used as
sqlite.<span><font color="#888888">
<div><br>
</div>
<div>Gilles Caulier</div>
</font></span></div>
<div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2016-07-22
19:31 GMT+02:00 Simon Frei <span
dir="ltr"><<a
moz-do-not-send="true"
href="mailto:freisim93@gmail.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:freisim93@gmail.com">freisim93@gmail.com</a></a>></span>:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div bgcolor="#FFFFFF"
text="#000000"> Compiled from
software-compilation. Git core
is on commit c9f02e0.
<div>
<div><br>
<br>
<div>On 22/07/16 19:14,
Gilles Caulier wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Which
digiKam version do you
use ?
<div><br>
</div>
<div>Gilles Caulier</div>
</div>
<div class="gmail_extra"><br>
<div
class="gmail_quote">2016-07-22
17:32 GMT+02:00
Simon Frei <span
dir="ltr"><<a
moz-do-not-send="true"
href="mailto:freisim93@gmail.com" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:freisim93@gmail.com">freisim93@gmail.com</a></a>></span>:<br>
<blockquote
class="gmail_quote"
style="margin:0 0
0
.8ex;border-left:1px
#ccc
solid;padding-left:1ex">Hi<br>
I do not have
enough detailed
information to
file a bug and
something similar
might already be
reported. Still I
wanted to inform
you about it.
Maybe it helps in
some way.<br>
I just made
changes to a big
set of images
(350G) outside of
digikam (metadata
writing with
exiftool). So it
took quite some
time searching for
new items after
startup
(notification on
the bottom left),
but never used cpu
or ram very hard.
After some time
however digikam
became
unresponsive, just
a grey frame. The
commandline did
show that it was
still working in
the background,
the following was
displayed
repeatedly:<br>
digikam.dimg:
"*somefile*" :
JPEG file
identified<br>
digikam.metaengine: Orientation => Exif.Image.Orientation => 1<br>
So digikam was
still functioning,
just not the gui
and still digikam
did load the
computer, but not
overload. After a
certain time
digikam resurfaced
and worked fine.<br>
Cheers,<br>
Simon<br>
_______________________________________________<br>
Digikam-devel
mailing list<br>
<a
moz-do-not-send="true"
href="mailto:Digikam-devel@kde.org" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:Digikam-devel@kde.org">Digikam-devel@kde.org</a></a><br>
<a
moz-do-not-send="true"
href="https://mail.kde.org/mailman/listinfo/digikam-devel"
rel="noreferrer"
target="_blank"><a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/digikam-devel">https://mail.kde.org/mailman/listinfo/digikam-devel</a></a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Digikam-devel mailing list
<a moz-do-not-send="true" href="mailto:Digikam-devel@kde.org" target="_blank">Digikam-devel@kde.org</a>
<a moz-do-not-send="true" href="https://mail.kde.org/mailman/listinfo/digikam-devel" target="_blank">https://mail.kde.org/mailman/listinfo/digikam-devel</a>
</pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Digikam-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:Digikam-devel@kde.org"
target="_blank">Digikam-devel@kde.org</a><br>
<a moz-do-not-send="true"
href="https://mail.kde.org/mailman/listinfo/digikam-devel"
rel="noreferrer"
target="_blank">https://mail.kde.org/mailman/listinfo/digikam-devel</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Digikam-devel mailing list
<a moz-do-not-send="true" href="mailto:Digikam-devel@kde.org" target="_blank">Digikam-devel@kde.org</a>
<a moz-do-not-send="true" href="https://mail.kde.org/mailman/listinfo/digikam-devel" target="_blank">https://mail.kde.org/mailman/listinfo/digikam-devel</a>
</pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Digikam-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:Digikam-devel@kde.org">Digikam-devel@kde.org</a><br>
<a moz-do-not-send="true"
href="https://mail.kde.org/mailman/listinfo/digikam-devel"
rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/digikam-devel</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Digikam-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Digikam-devel@kde.org">Digikam-devel@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/digikam-devel">https://mail.kde.org/mailman/listinfo/digikam-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>