OTRS-6: Ticket with 122 articles causes cgi 100% CPU and unresponsive

--===============5536707960463470234==
Content-Type: multipart/alternative; boundary="0000000000009b99c0059b4735c4"

--0000000000009b99c0059b4735c4
Content-Type: text/plain; charset="UTF-8"

Greetings,

I have (had) a well functioning OTRS6 system until a ticket hit 120+
articles. Now when that ticket is opened by an agent the browser becomes
unresponsive and the server otrs/cgi process hits 100% CPU and stays there.

Ver: 6.0.11
OS: CentOS 7.7 x86_64, Apache2, mod_perl
DB: mariadb
Host: 4CPU(2.4GHz) 12GB RAM VMWare VM on quad socket Opteron host. SSD
storage.
Backend mail: IMAP

In an attempt to fix this I have archived many old closed tickets.
Optimized the tables in mariadb, used mod_perl. Even tried dialing
down Ticket::Frontend::MaxArticlesPerPage
and Ticket::Frontend::MaxArticlesZoomExpand down to 10 in hopes of limiting
the amount of articles opened or indexed when the ticket was zoomed (or
looked at from agent view).

None of that worked. Throwing hardware (cores, ram) doesn't fix it.

Do I split the ticket? Is there a setting where it won't try and open all
122 articles just to display the most recent article?

Thanks!

--0000000000009b99c0059b4735c4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Greetings,<div><br></div><div>I have (had) a well function=
ing OTRS6 system until a ticket hit 120+ articles. Now when that ticket is =
opened by an agent the browser becomes unresponsive and the server otrs/cgi=
 process hits 100% CPU and stays there.</div><div><br></div><div>Ver: 6.0.1=
1</div><div>OS: CentOS 7.7 x86_64, Apache2, mod_perl</div><div>DB: mariadb<=
/div><div>Host: 4CPU(2.4GHz) 12GB RAM VMWare VM on quad socket Opteron host=
. SSD storage.</div><div>Backend mail: IMAP</div><div><br></div><div>In an =
attempt to fix this I have archived many old closed tickets. Optimized the =
tables in mariadb, used mod_perl. Even tried dialing down=C2=A0Ticket::Fron=
tend::MaxArticlesPerPage and=C2=A0Ticket::Frontend::MaxArticlesZoomExpand d=
own to 10 in hopes of limiting the amount of articles opened or indexed whe=
n the ticket was zoomed (or looked at from agent view).=C2=A0</div><div><br=
></div><div>None of that worked. Throwing hardware (cores, ram) doesn&#39;t=
 fix it.=C2=A0</div><div><br></div><div>Do I split the ticket? Is there a s=
etting where it won&#39;t try and open all 122 articles just to display the=
 most recent article?</div><div><br></div><div>Thanks!</div></div>

--0000000000009b99c0059b4735c4--

--===============5536707960463470234==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs

--===============5536707960463470234==--