Bug 447971 - Gwenview is EXTREMELY slow being a native application in KDE Plasma
Summary: Gwenview is EXTREMELY slow being a native application in KDE Plasma
Status: RESOLVED DUPLICATE of bug 445176
Alias: None
Product: gwenview
Classification: Applications
Component: general (show other bugs)
Version: 21.11.90
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Gwenview Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-05 12:32 UTC by Rafael Linux User
Modified: 2022-01-12 20:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rafael Linux User 2022-01-05 12:32:36 UTC
SUMMARY
***
Thumbnails generation is EXTREMELY slow in Gwenview. Don't know why. Is not a specific scenario issue. You can try yourself in any system and compare with XnView MP (that finally is what I'm using, cause I have more tan 50k photos).
***


STEPS TO REPRODUCE
1.  Open a remote (NFS shared) folder with 100 photos in Gwenview and see how long does it takes to begin to show photos thumbnails and to show ALL 100 photos.
2.  Open a remote (NFS shared) folder with 100 photos in XnView MP and see how long does it takes to begin to show photos thumbnails and to show ALL 100 photos.


OBSERVED RESULT
 XnView is about 4x tiimes faster than Gwenview, being Gwenview a native application of KDE.

EXPECTED RESULT
Gwenview should be at least as fast as XnView, also taking into account that XnView show a lot of additional info below each photo and icons about photo properties.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20211203
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.15.5-1-default (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 2060/PCIe/SSE2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2022-01-12 20:24:47 UTC
*** This bug has been marked as a duplicate of bug 445176 ***