Kernel Newbies archive mirror
 help / color / mirror / Atom feed
From: Naruto Nguyen <narutonguyen2018@gmail.com>
To: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: How to debug high sysload in 2,3 second
Date: Mon, 15 May 2023 18:58:33 +1000	[thread overview]
Message-ID: <CANpxKHGB8Q+98Vt8K85EMVnCBc4pzc85qhhmqmvEi6ZXHkW1Ww@mail.gmail.com> (raw)

Hi everyone,

My system during idle sometimes has high sysload in 2,3 seconds
(around 70% sysload) and then come back to normal after that. I see it
happen in some conditions and try to use top commands to debug and see
one of processes in my system consume CPU.

I would like to investigate more what code causes CPU high. However
the spike only happens 2,3 seconds so I have no ideas to continue
debugging. I thought about perf tool, but I am not sure how to profile
with perf to identify exactly what happens in 2,3 seconds during high
CPU. Because I can reproduce the issue to see it, but only during 3 or
4 minutes, I can see CPU increase in 2,3 seconds. So I worry that
using perf to profile in 3,4 minutes cannot identify the code causing
CPU increase in a short time.

Could you help to advise how I can debug in this case?

Thanks,
Brs,
Naruto

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

             reply	other threads:[~2023-05-15  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15  8:58 Naruto Nguyen [this message]
2023-05-16 10:44 ` How to debug high sysload in 2,3 second Valdis Klētnieks
2023-05-16 21:44   ` Valentin Vidić

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANpxKHGB8Q+98Vt8K85EMVnCBc4pzc85qhhmqmvEi6ZXHkW1Ww@mail.gmail.com \
    --to=narutonguyen2018@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).