From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 288EA158083 for ; Thu, 5 Sep 2024 22:14:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7388FE2A4A; Thu, 5 Sep 2024 22:14:38 +0000 (UTC) Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0AE0AE2A3B for ; Thu, 5 Sep 2024 22:14:37 +0000 (UTC) Received: by mail-lf1-x132.google.com with SMTP id 2adb3069b0e04-536536f6f8fso180186e87.1 for ; Thu, 05 Sep 2024 15:14:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725574476; x=1726179276; darn=lists.gentoo.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=ImFhwfGqWqDPP1bn8yV3rSOPmrxEINEMQMqorJQLZ2s=; b=dlfwzm1+rtchWohuzL2boUFQM3ThAi9xFMxRrA9jvB3aUAG+ex9OZ7+E/829blOQkq SvPNKZQvyRQ7vgmc2w/KLp7XPu+dM9THnLxk3nrOLuhXOpl4d2NnG4H+6ZNcOViXLC52 bcPv8JxSTais+48w2B6LDCISTYw/K1JHWfM/izz4R7CHlr8S8vrPPR2WTEOga0De9AGl XzFY/nHNbOfSrVhb8JoAZmQItLi5/QdwDrQSF3+6Yx6bC2P4IaskpEnggMdIFNhdybL+ yB5iw7ZsXWCyk/eX6J1m6dbir58Vw21ZqjfI0hTpw5345TEQcorz43uOtJk63bfvMrFR Shkg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725574476; x=1726179276; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ImFhwfGqWqDPP1bn8yV3rSOPmrxEINEMQMqorJQLZ2s=; b=dfLpVSHptg9AvU6Pot0SO8qS7Ewo1HaOZbTjH0b4UvUMN+LPZnCD8IMm6pzAIsJMI4 Bx6r18qHFWZGtrVpmJdnA+CkZ78kh+iV7QfrzeqtVpb83DY6wPNiUAFURhW2rcjGhB1Y cfUbt1gBojoIhBRzaGQOehzLkPhaYrCfue/jkniPtkB2rgaYO8WVVnmHGc4HKSBB8+Fv ++lXZY/VFTi/S78Z1H2bhA8PBZBLUp4Di9n8WTxUoEjiU2VQV1HWgPppDybH4PZ3duUj aL/72vR8VUp1M32tF1auiwHyjDkPJAkMLUxHh/zlxEx0N+Pu/h77vBegp4l6gVNcSTCD 1J9A== X-Gm-Message-State: AOJu0YyV0yRgypHqFETsUcYwVK0JHGBLohUiFehtGMCLvCT6HxY5x70G jAnY0/Hrm1W94IrYDhVQ9buobcpExATz4U5aHuIBqjYI7eTjln9XrvSxHTH/bjW0jZ1LhAfAKMg p8w4spBFyR4FJ7+wpvXyiBFTeZKbt+Q== X-Google-Smtp-Source: AGHT+IGEOPktt62VT9yGc5EIkC/UZ9xR002P7qGgU5TXi9NFg1xGXyWTF+FKtQbqGS118soajrqmF35cFHRVRItkbw0= X-Received: by 2002:a05:6512:3b07:b0:535:4144:e682 with SMTP id 2adb3069b0e04-5365882ef1bmr75535e87.11.1725574475797; Thu, 05 Sep 2024 15:14:35 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <5814876.DvuYhMxLoT@cube> <6090690.lOV4Wx5bFT@cube> <5815640.DvuYhMxLoT@cube> <2746872.mvXUDI8C0e@cube> In-Reply-To: <2746872.mvXUDI8C0e@cube> From: Mark Knecht Date: Thu, 5 Sep 2024 15:14:24 -0700 Message-ID: Subject: Re: [gentoo-user] Wayland and CPU load To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary="000000000000a9dbf20621669d37" X-Archives-Salt: f1579a6a-4781-433d-a002-90d207627885 X-Archives-Hash: 34fef95174c234066c6f76031945d551 --000000000000a9dbf20621669d37 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Sep 5, 2024 at 12:00=E2=80=AFPM Peter Humphrey 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 --000000000000a9dbf20621669d37 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Sep 5, 2024 at 12:00=E2=80=AFPM Peter Hump= hrey <peter@prh.myzen.co.uk= > wrote:
>
> On Thursday 5 September 2024 15:43:00 BST Iwrot= e:
> > 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 visib= le in /top/.
> >
> > Much improved, but it still isn'= t right.
>
> It came back again, so I ran a complete -e, reboot= ed, recompiled the kernel
> again and rebooted again.
>
>= It's all back as it was - no CPU cycles left for anything else but way= land and
> plasam-shell.
>
> How to debug this?
>> --
> Regards,
> Peter.

If you are running sy= stemd then you can try=C2=A0

systemd-cgtop

which should identify what slice, if any, is using lots o= f CPU.

If you were interested in exploring more de= eply you might
be able to create a control group that Wayland cou= ld run
inside of to limit resources or possible identify what
part of Wayland is getting out of control
--000000000000a9dbf20621669d37--