You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@commons.apache.org by Andreas Kuhtz <an...@gmail.com> on 2023/05/15 16:25:05 UTC

[daemon] High CPU load after update from 1.3.2 to 1.3.3

Hi there,

I see a high CPU load after updating commons-daemon from 1.3.2 to 1.3.3
(and 1.3.4) on my system.
The application is a simple SpringBoot application that is started with
service-user LocalSystem (no difference if started with default value).

How can I find the cause for this?

Many thanks,
Andreas

Re: [daemon] High CPU load after update from 1.3.2 to 1.3.3

Posted by Andreas Kuhtz <an...@gmail.com>.
Hello,

I know that the statement "high CPU load" ist pretty vague, but the CPU
load in Windows task manager was the only visible thing I saw. No different
logs even with LogLevel=DEBUG.

But I found out that removing the StopTimeout parameter (in my case
--StopTimeout=15) solves the issue. So I think it might be related to this
change:
https://github.com/apache/commons-daemon/commit/243a8521f780b98247820ae187e395597f6c9b51#diff-b4e825062840bfdafb7eeed624d22a66257983305ca7e21470b679bff4ef1ffeR1840-R1850



Am Mo., 15. Mai 2023 um 21:08 Uhr schrieb
<Jo...@wellsfargo.com.invalid>:

> Andreas,
>
> Use the java flight recorder to take a recording of a minute or two.  Open
> it in Java Mission Control and look at the method samples.  That will give
> you a good idea where the CPU usage is coming from.  If that doesn't seem
> helpful, maybe enable -XX+DebugNonSafepoints and try again.
>
>
> > -----Original Message-----
> > From: Andreas Kuhtz <an...@gmail.com>
> > Sent: Monday, May 15, 2023 11:25 AM
> > To: user@commons.apache.org
> > Subject: [daemon] High CPU load after update from 1.3.2 to 1.3.3
> >
> > Hi there,
> >
> > I see a high CPU load after updating commons-daemon from 1.3.2 to 1.3.3
> > (and 1.3.4) on my system.
> > The application is a simple SpringBoot application that is started with
> service-
> > user LocalSystem (no difference if started with default value).
> >
> > How can I find the cause for this?
> >
> > Many thanks,
> > Andreas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>

RE: [daemon] High CPU load after update from 1.3.2 to 1.3.3

Posted by Jo...@wellsfargo.com.INVALID.
Andreas,

Use the java flight recorder to take a recording of a minute or two.  Open it in Java Mission Control and look at the method samples.  That will give you a good idea where the CPU usage is coming from.  If that doesn't seem helpful, maybe enable -XX+DebugNonSafepoints and try again.


> -----Original Message-----
> From: Andreas Kuhtz <an...@gmail.com>
> Sent: Monday, May 15, 2023 11:25 AM
> To: user@commons.apache.org
> Subject: [daemon] High CPU load after update from 1.3.2 to 1.3.3
> 
> Hi there,
> 
> I see a high CPU load after updating commons-daemon from 1.3.2 to 1.3.3
> (and 1.3.4) on my system.
> The application is a simple SpringBoot application that is started with service-
> user LocalSystem (no difference if started with default value).
> 
> How can I find the cause for this?
> 
> Many thanks,
> Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org


Re: [daemon] High CPU load after update from 1.3.2 to 1.3.3

Posted by Gary Gregory <ga...@gmail.com>.
The statement "high CPU load" is pretty vague. Gathering data on which
processes use what percentage of CPU/cores and disk activity over time
would be a start.

Gary

On Mon, May 15, 2023, 12:25 Andreas Kuhtz <an...@gmail.com> wrote:

> Hi there,
>
> I see a high CPU load after updating commons-daemon from 1.3.2 to 1.3.3
> (and 1.3.4) on my system.
> The application is a simple SpringBoot application that is started with
> service-user LocalSystem (no difference if started with default value).
>
> How can I find the cause for this?
>
> Many thanks,
> Andreas
>