From: "Valentin Vidić" <vvidic@valentin-vidic.from.hr>
To: kernelnewbies@kernelnewbies.org
Subject: Re: How to debug high sysload in 2,3 second
Date: Tue, 16 May 2023 23:44:53 +0200 [thread overview]
Message-ID: <ZGP5VWbCsdwfNKmf@valentin-vidic.from.hr> (raw)
In-Reply-To: <568575.1684233860@turing-police>
On Tue, May 16, 2023 at 06:44:20AM -0400, Valdis Klētnieks wrote:
> You could always leave 'top' running with a 0.5 or 1 second refresh in a
> terminal window, point some sort of video camera at the screen, and after
> you've reproduced it go back and look at the video frame-by-frame until you
> find the 'top' refresh(es) that happened during the high load.
You can also try atop as it has the ability to record and report short
running userspace processes that consume a lot of CPU.
--
Valentin
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2023-05-16 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 8:58 How to debug high sysload in 2,3 second Naruto Nguyen
2023-05-16 10:44 ` Valdis Klētnieks
2023-05-16 21:44 ` Valentin Vidić [this message]
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=ZGP5VWbCsdwfNKmf@valentin-vidic.from.hr \
--to=vvidic@valentin-vidic.from.hr \
--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).