https://bugs.kde.org/show_bug.cgi?id=431037
--- Comment #9 from LarsE <ristrett...@live.com> --- Sorry that it took some time to come back with my results from testing, but spare-time was quite limited during the last weeks ;-) I did some research and updated my mariadb installation from 10.5.4 (which indeed had some performance issues) to 10.5.8 (in which those issues were fixed according to the release notes). After the database update, I ran some performance tests with sysbench 1.0.18 (LuaJIT 2.1.0-beta3) against a mariadb test instance of 10.000 rows: As an average I got - 37 transactions per second - 747 queries per second I also checked my network performance with iperf3 between the Windows client and the Linux server running mariadb and the NAS storage. iperf3 showed me the following numbers: Ethernet (1GBit LAN) ==================== 1 stream -> 894 MBit/s 2 stream -> 918 MBit/s (gain +3%) WiFi (802.11ac, 2*2 MIMO) ========================= 1 stream -> 257 MBit/s 2 stream -> 375 MBit/s (gain +45%) 3 stream -> 406 MBit/s (gain +8%) 4 stream -> 423 MBit/s (gain +4%) My WiFi router is capable of 430MBit/s net data rate, when using AC 2*2 MIMO. I also did some more testing with 7.2.0 beta1 (WiFi+LAN) and 7.2.0 beta2 (LAN) to get some more performance numbers. My test procedure was as follows: - start Digikam with an empty (=no albums) database 1. set a network folder containing 18 raw (with sidecars) 18 JPG (without sidecars) 2. Having lazy sync set, assign two tags to 18 JPG pictures 3. Sync the files - quit the software - reset the database (drop and re-create) Please kindly have a look at the logs that I uploaded. The summary is as follows: 7.2.0-beta1 WIFI ================ 1. ends 704.81 (complete scan 595,426s) 2. assign tags 1st tag start: 781.98 (took 62,68s) 2nd tag start: 878.55 (took 56,4s) 3. start: 1082 (took 12,71s) 7.2.0-beta1 LAN =============== 1. ends 384.55 (complete scan 298,478s) 2. assign tags 1st tag start: 718.71 (took 46,18s) 2nd tag start: 865.27 (took 42,26s) 3. start: 985 (took 4,26s) 7.2.0-beta2 LAN =============== 1. ends 471.56 (complete scan 392,204s) 2. assing tags 1st tag start: 528.07 (took 54,7s) 2nd tag start: 632.21 (took 21s) 3. start: 670.52 (took 4,26s) That data given, I would like to ask if you think that the performance is normal / to be expected for that configuration of database, WiFi and LAN. Or if you see something that might be optimized to increase performance. Thanks in advance for all your work and time you put into this nice project and my call in special. Bye, Lars. P.S.: I didn't do a test using a unc path, since from my experience using the unc path is typically less performant under Windows than using a network drive. -- You are receiving this mail because: You are watching all bug changes.
