Forum: >>> Magnum BBS <<<

Bug#1092963: korganizer: Each action in Korganizer are extremely slow s

From Alexandre Bonneau@21:1/5 to All on Mon Mar 24 16:26:41 2025

This is a multi-part message in MIME format.

--nextPart2954640.FA0FI3ke8A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

That sqlite3 metric is interesting indeed.

However even after the few upgrades to kdepim and korganizer since I opened this bug,
hoping they would fix this critical problem, the problem is still present: korganizer 4:24.12.2-1
kdepim 4:24.12.2+5.158
kdepimruntime 4:24.12.2-1
akonadiserver 4:24.12.2-1

As a sidenote I upgraded my computer to a Ryzen 9 X3D, and I can noticeably see that
when moving tasks or events around, it takes a few seconds less.
Everything seems to point to the fact that this slow response time is CPU-bound.

Not sure if this is related, but that bad Korganizer upgrade also broke at least 2 things:
- When using tags with accents in it, Korganizer mangle it so that for instance "é" appears
as "Ã©", creating new faulty tags in the tags list.
- Sometimes when you edit a calendar task or event, the tags are just plain removed (even
if they do not contains any accent), which updates the events on Nextcloud, which are
replicated without any tags on the correct Korganizer clients (from Debian stable).

This is especially annoying on past meetings with other people where if you want to 'fix'
the missing tag, you need to edit the event..which will send the 'update' to every
attendees. Not possible in a work environement.

To sum up, before having 10k+ event was not a problem, now it is. Where do we go from
here?

Regards,
Alexandre Bonneau

Le mardi 14 janvier 2025, 10:17:12 heure de Tahiti Soren Stoutner a écrit :

On Monday, January 13, 2025 7:09:06 PM MST Alexandre Bonneau wrote:

Which database type are you using ?

» dlg akonadi
rc akonadi-backend-mysql 4:22.12.2-1
ii akonadi-backend-sqlite 4:24.12.0-2

I’m a little puzzled that you have 22.x for mysql and 24.x for sqlite. Testing currently has 24.x for both of them.

Although this doesn’t directly address your particular bug, which appears to
maybe be something that happens with large amounts of calendar entries, you might be interested in the discussion about how much faster sqlite runs compared to postgresql (and possibly mariadb).

https://lists.debian.org/debian-kde/2024/12/msg00079.html

--nextPart2954640.FA0FI3ke8A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>That sqlite3 metric is interesting indeed.
 However even after the few upgrades to kdepim and korganizer since I opened this bug, hoping they would fix this critical problem, the problem is still present:
korganizer 4:24.12.2-1
kdepim 4:24.12.2+5.158
kdepimruntime 4:24.12.2-1
akonadiserver 4:24.12.2-1
 As a sidenote I upgraded my computer to a Ryzen 9 X3D, and I can noticeably see that when moving tasks or events around, it takes a few seconds less.
Everything seems to point to the fact that this slow response time is CPU-bound.
 Not sure if this is related, but that bad Korganizer upgrade also broke at least 2 things:
- When using tags with accents in it, Korganizer mangle it so that for instance "é" appears as "Ã©", creating new faulty tags in the tags list.
- Sometimes when you edit a calendar task or event, the tags are just plain removed (even if they do not contains any accent), which updates the events on Nextcloud, which are
replicated without any tags on the correct Korganizer clients (from Debian stable).
 This is especially annoying on past meetings with other people where if you want to 'fix' the missing tag, you need to edit the event..which will send the 'update' to every
attendees. Not possible in a work environement.
 To sum up, before having 10k+ event was not a problem, now it is. Where do we go from here?
 Regards,
Alexandre Bonneau
 Le mardi 14 janvier 2025, 10:17:12 heure de Tahiti Soren Stoutner a écrit :
> On Monday, January 13, 2025 7:09:06 PM MST Alexandre Bonneau wrote:
> > > > Which database type are you using ?
> > > 
> > > » dlg akonadi
> > > rc  akonadi-backend-mysql    4:22.12.2-1
> > > ii  akonadi-backend-sqlite      4:24.12.0-2
> > I’m a little puzzled that you have 22.x for mysql and 24.x for sqlite.
> Testing currently has 24.x for both of them.
> > Although this doesn’t directly address your particular bug, which appears to
> maybe be something that happens with large amounts of calendar entries, you
> might be interested in the discussion about how much faster sqlite runs
> compared to postgresql (and possibly mariadb).
> > https://lists.debian.org/debian-kde/2024/12/msg00079.html
 </body>
</html>
--nextPart2954640.FA0FI3ke8A--

-----BEGIN PGP SIGNATURE-----

iF0EABEKAB0WIQRbWzskGLftNYMKah8bd6g6OLvBPgUCZ+IUYQAKCRAbd6g6OLvB Pvl2AJ9wmWZvlk3wp8HBEsHfESqI+PK7QwCgv+mZLpcdiNvT3BxdCldBrsGyp98=
=lyxQ
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Patrick Franz@21:1/5 to alexandre.bonneau@linuxfr.eu on Sun May 4 12:40:02 2025

Hi,

On Mon, 24 Mar 2025 16:26:41 -1000 Alexandre Bonneau <alexandre.bonneau@linuxfr.eu> wrote:
[...]

To sum up, before having 10k+ event was not a problem, now it is.
Where do we go from here?

I don't really know how to debug this. The only thing I can recommend is
to file a bug upstream. They should be able to debug it.

--
Med vänliga hälsningar

Patrick Franz

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Alexandre Bonneau@21:1/5 to All on Mon May 5 12:50:02 2025

This is a multi-part message in MIME format.

Hi,

I declared the bug upstream there: https://bugs.kde.org/show_bug.cgi?id=501965[1]
Since this makes Korganizer unusable, but there has been not much activity for a month, I
fear the fix will not come soon..

Regards,
Alexandre Bonneau

Le dimanche 4 mai 2025, 00:34:44 Patrick Franz a écrit :

Hi,

On Mon, 24 Mar 2025 16:26:41 -1000 Alexandre Bonneau <alexandre.bonneau@linuxfr.eu> wrote:
[...]

To sum up, before having 10k+ event was not a problem, now it is.
Where do we go from here?

I don't really know how to debug this. The only thing I can recommend is
to file a bug upstream. They should be able to debug it.

--------
[1] https://bugs.kde.org/show_bug.cgi?id=501965

<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>    Hi,
 I declared the bug upstream there: <a href="https://bugs.kde.org/show_bug.cgi?id=501965">https://bugs.kde.org/show_bug.cgi?id=501965</a>
Since this makes Korganizer unusable, but there has been not much activity for a month, I fear the fix will not come soon..
 Regards,
Alexandre Bonneau
 Le dimanche 4 mai 2025, 00:34:44 Patrick Franz a écrit :
> Hi,
> > On Mon, 24 Mar 2025 16:26:41 -1000 Alexandre Bonneau
> <alexandre.bonneau@linuxfr.eu> wrote:
> [...]
> > > To sum up, before having 10k+ event was not a problem, now it is.
> > Where do we go from here?
> > I don't really know how to debug this. The only thing I can recommend is
> to file a bug upstream. They should be able to debug it.
 </body>
</html>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Who's Online

System Info

Sysop:	Keyop
Location:	Huddersfield, West Yorkshire, UK
Users:	489
Nodes:	16 (2 / 14)
Uptime:	36:57:27
Calls:	9,669
Files:	13,716
Messages:	6,169,425

Bug#1092963: korganizer: Each action in Korganizer are extremely slow s

Who's Online

System Info