[digikam] [Bug 325653] MIGRATION : database conversion is very slow

2023-10-12 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=325653

soredake  changed:

   What|Removed |Added

 CC|broaden_acid002@simplelogin |
   |.com|

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 325653] MIGRATION : database conversion is very slow

2023-10-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=325653

--- Comment #11 from caulier.gil...@gmail.com ---
Thomas,

What's about this file using current 8.2.0 AppImage Linux bundle ? It's
reproducible ?

https://files.kde.org/digikam/

Note: bundle is now based on Qt 5.15.11 and KDE framework 5.110.

Thanks in advance

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 325653] MIGRATION : database conversion is very slow

2023-05-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=325653

caulier.gil...@gmail.com changed:

   What|Removed |Added

Version|3.3.0   |8.0.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 325653] MIGRATION : database conversion is very slow

2023-05-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=325653

tim...@timmib.de changed:

   What|Removed |Added

 CC||tim...@timmib.de

--- Comment #10 from tim...@timmib.de ---
Hi, yes i can reproduce it with digiKam-8.0.0-x86-64.appimage.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 325653] MIGRATION : database conversion is very slow

2023-04-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=325653

--- Comment #9 from caulier.gil...@gmail.com ---
Hi all,

digiKam 8.0.0 is out. Problem still reproducible ?

Best regards
Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 325653] MIGRATION : database conversion is very slow

2022-05-21 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=325653

soredake  changed:

   What|Removed |Added

 CC||ndrzj1...@relay.firefox.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 325653] MIGRATION : database conversion is very slow

2022-01-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=325653

--- Comment #8 from caulier.gil...@gmail.com ---
Hi Thomas and happy new year,

Can you reproduce the problem with digiKam 7.5.0 pre-release AppImage bundle
for
Linux available here :

https://files.kde.org/digikam/

Best regards

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 325653] MIGRATION : database conversion is very slow

2020-08-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=325653

--- Comment #7 from caulier.gil...@gmail.com ---
digiKam 7.0.0 stable release is now published:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Best regards

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 325653] MIGRATION : database conversion is very slow

2018-02-26 Thread Michał Karwowski
https://bugs.kde.org/show_bug.cgi?id=325653

Michał Karwowski  changed:

   What|Removed |Added

 CC||pro...@gmail.com

--- Comment #6 from Michał Karwowski  ---
I'm confirming, that in DigiKam 5.8.0 - migration from MySQL to SQLite is very
slow.

To speed up, I have created RAM disk to store SQLite database, but still, it
takes ages.

I notice, that during migration .jurnal file is created and deleted over and
over again.

That's why I think it might be related to single insert transaction commits.

According to http://www.sqlite.org/faq.html#q19
---
Transaction speed is limited by disk drive speed because (by default) SQLite
actually waits until the data really is safely stored on the disk surface
before the transaction is complete. That way, if you suddenly lose power or if
your OS crashes, your data is still safe. For details, read about atomic commit
in SQLite..

By default, each INSERT statement is its own transaction. But if you surround
multiple INSERT statements with BEGIN...COMMIT then all the inserts are grouped
into a single transaction. The time needed to commit the transaction is
amortized over all the enclosed insert statements and so the time per insert
statement is greatly reduced.
--

Thus probably it would be a good idea to wrap inserts by some transaction.



Moreover, we could try to do some tweaks to improve performance.
We can ask SQLite not to delete and recreate file over and over again for each
insert, by using PRAGMA JOURNAL_MODE.
With value eg. 'TRUNCATE', we can keep journal file, but it will be cleared.

If we can accept loose of imported data on eg power failure, we can use some
pragmas to speed up.

See: https://blog.devart.com/increasing-sqlite-performance.html
See:
https://stackoverflow.com/questions/1711631/improve-insert-per-second-performance-of-sqlite

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 325653] MIGRATION : database conversion is very slow

2017-12-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=325653

--- Comment #5 from caulier.gil...@gmail.com ---
With next 5.8.0 release Mysql support have been well improved and a lots of
bugs fixed.

Please test with pre release 5.8.0 bundles that we provide and give us a
feedback

https://files.kde.org/digikam/

Thanks in advance

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 325653] MIGRATION : database conversion is very slow

2016-12-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=325653

--- Comment #4 from caulier.gil...@gmail.com ---
Can you reproduce the problem using digiKam Linux AppImage bundle ? The last
bundle is available at this url:

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 325653] MIGRATION : database conversion is very slow

2016-07-10 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=325653

--- Comment #3 from caulier.gil...@gmail.com ---
And with 4.9.0, the problem is reproducible ?

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 325653] MIGRATION : database conversion is very slow

2016-07-10 Thread Thomas Bleher via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=325653

--- Comment #2 from Thomas Bleher  ---
Sorry, at the moment I don't have time to update to digiKam 5.0.0 and set up
appropriate tests (still on digiKam 4.9.0).

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 325653] MIGRATION : database conversion is very slow

2016-07-06 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=325653

--- Comment #1 from caulier.gil...@gmail.com ---
This file still valid using last digiKam 5.0.0 ?

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.