[Digikam-devel] [Bug 302131] New: Xp client, linux MySql server slow startup

[Tex]

https://bugs.kde.org/show_bug.cgi?id=302131

            Bug ID: 302131
          Severity: normal
           Version: 2.5.0
          Priority: NOR
          Assignee: digikam-devel at kde.org
           Summary: Xp client, linux MySql server slow startup
    Classification: Unclassified
                OS: MS Windows
          Reporter: Tex2571 at hotmail.com
          Hardware: MS Windows
            Status: UNCONFIRMED
         Component: general
           Product: digikam

NOT just another slow startup bug, I hope.

I have a Fedora server serving about 20K pics  over smb/cifs and hosting a
MySQL server for the digikam databse.

I have two clients, one XP and one linux. (I edited the AlbumsRoot table in the
database with the "&" trick:
https://bugs.kde.org/show_bug.cgi?id=261277,
 to inlcude both the linux and windows mount path so that both machines can use
the same database, and that works!! Yay.)

The xp client was setup with the 2.5 windows digikam installer.  With or
without  scan at startup selected, it starts SLOW. (maybe slower with than
without, not sure)  It takes many minutes, probably about 8, during "scanning
database".

I monitor with atop on the server.  Myslqd runs for one atop refresh  with some
I/O  and then calms back down to 0 I/O and 0 CPU.
smbd though runs the whole time at high cpu load , but reading and writing only
small amounts of data (like 8K per 5 sec. refresh usually), so maybe scanning
file trees?  Mysqld is doing relatively little.

The networking is gigabit but limited by hardware to about 20 to 30 MBytes/s,
not exactly turtle slow.  

Now I have a second linux client accessing the exact same database also using
digikam 2.5.

On the linux box digikam starts up in a couple of seconds even with scan images
on startup selected.  I see the initial burst of database activity on atop, and
that's it... then it's started.

This makes digikam on xp unusable, especially considering it crashes from time
to time.

Also when adding a new local collection on the XP machine, a scan was started,
with similar behavior and a similar delay.

-- 
You are receiving this mail because:
You are the assignee for the bug.