https://bugs.kde.org/show_bug.cgi?id=481389
Bug ID: 481389
Summary: Possible "fix" for reliability issues
Classification: Applications
Product: kdeconnect
Version: unspecified
Platform: Debian unstable
OS: Linux
Status: REPORTED
Keywords: efficiency, reproducible, usability
Severity: normal
Priority: NOR
Component: messaging-application
Assignee: si...@ergotech.com
Reporter: kde.i6...@simplelogin.com
Target Milestone: ---
STEPS TO REPRODUCE
Attempt to use KDE Connect with years of messages saves on SIM (in my case,
165k+)
OBSERVED RESULT
Lagging interface, messages not loading/sending, etc. Inconsistent performance
and issues with usability as messages continue to load each time the desktop
application is launched. Have observed messages "lost" on send, unexpected
loading behavior, etc.
EXPECTED RESULT
The ability to receive and send SMS messages.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 6.6.15-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 6800 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X570 AORUS MASTER
System Version: -CF
PROPOSAL:
When I began looking at this I thought the original fix to this issue might be
caching messages to a local DB and revising that implementation, but I have had
another idea I want to share with the developer. I think may take significantly
less time and testing. I believe this is observed behavior that is behind many
bug reports on this site, and off-site threads I have observed exploring
KDEConnect (stack, reddit, etc.).
I have deleted over 130k of my messages to reduce the SMS load to a more
reasonable "1 year of history" and have roughly 35k messages. With this done,
the app is snappy and works great, as expected.
I believe allowing a configuration setting for the plugin (or perhaps it best
lives in the KDEConnect app to reduce SMS parsing?) to only load the last "X"
messages or since "Y" date would fix many performance issues and give 99% of
users the experience they are looking for - the ability to respond to
relatively recent messages with snappy performance and reliable transit,
without adding additional logic to caching messages or establishing new
databases/data integrity.
I believe most users want to respond to current messages, or messages from
recent memory, when using this program effectively. Adding these settings would
be a "low cost" way to address performance issues for large SIM databases
without asking users to delete messages from their record source. Thanks for
your consideration.
--
You are receiving this mail because:
You are watching all bug changes.
