From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Wayland and CPU load
Date: Thu, 5 Sep 2024 15:14:24 -0700 [thread overview]
Message-ID: <CAK2H+efEfQ-_KHmKXxyN4Gf5Fy_L_XguCTp=zsmdS4MYW5FYwg@mail.gmail.com> (raw)
In-Reply-To: <2746872.mvXUDI8C0e@cube>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
On Thu, Sep 5, 2024 at 12:00 PM Peter Humphrey <peter@prh.myzen.co.uk>
wrote:
>
> On Thursday 5 September 2024 15:43:00 BST Iwrote:
> > On Thursday 5 September 2024 13:47:29 BST I wrote:
> > > ... Perhaps I should start recompiling things...
> >
> > After an emerge -e1 kwayland plasma-workspace and a reboot,
kwin_wayland is
> > down to 20-60% CPU and plasma_shell is barely visible in /top/.
> >
> > Much improved, but it still isn't right.
>
> It came back again, so I ran a complete -e, rebooted, recompiled the
kernel
> again and rebooted again.
>
> It's all back as it was - no CPU cycles left for anything else but
wayland and
> plasam-shell.
>
> How to debug this?
>
> --
> Regards,
> Peter.
If you are running systemd then you can try
systemd-cgtop
which should identify what slice, if any, is using lots of CPU.
If you were interested in exploring more deeply you might
be able to create a control group that Wayland could run
inside of to limit resources or possible identify what
part of Wayland is getting out of control
[-- Attachment #2: Type: text/html, Size: 1398 bytes --]
next prev parent reply other threads:[~2024-09-05 22:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 6:32 [gentoo-user] Wayland and CPU load Peter Humphrey
2024-09-05 7:50 ` Michael
2024-09-05 12:47 ` Peter Humphrey
2024-09-05 14:43 ` Peter Humphrey
2024-09-05 19:00 ` Peter Humphrey
2024-09-05 21:29 ` Michael
2024-09-05 23:21 ` Peter Humphrey
2024-09-06 0:33 ` Peter Humphrey
2024-09-06 9:10 ` Michael
2024-09-06 9:45 ` Peter Humphrey
2024-09-06 10:41 ` Michael
2024-09-06 11:30 ` Peter Humphrey
2024-09-05 22:14 ` Mark Knecht [this message]
2024-09-05 15:08 ` Peter Humphrey
2024-09-05 16:27 ` Michael
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='CAK2H+efEfQ-_KHmKXxyN4Gf5Fy_L_XguCTp=zsmdS4MYW5FYwg@mail.gmail.com' \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.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