From nobody Sun Oct 9 05:58:52 2022 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4MlWZl0XZYz4drRP for ; Sun, 9 Oct 2022 05:59:11 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4MlWZk29fzz45Nv for ; Sun, 9 Oct 2022 05:59:10 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-io1-xd29.google.com with SMTP id e205so6438311iof.1 for ; Sat, 08 Oct 2022 22:59:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=xvLTNFWlMvg+HY64rDNvkGcJ0i15FJbhkNuqG+SNYeY=; b=eB7VW61QJw9iP4VthfkxknMIQnYNMyPBx00IlFXyQLHis6WX8iw/PV5LjLHYS7lPFJ EWRt1dbohcNW5gE1pAqR79Tkbtg0z0dWR0Xu6dep1wF+FegpD/Cq7XpOWMXoV8ebB68y o4goyXMQc6v4C0/3ceS4uHjdov6DRWCR1cvocU4OVM3TUozT13qJA/bWHeAzO/qmby2b TTz/gUzKWBQZiTjoTJIBt+QA0tnah5e4MLMjBPt1NoyPBugxP0ZiGusykURatCIKHfAi p7jeuCxw0Puu6Q2lqT2tMyd2cy/Iwp45ixvdxLlYxs9Y5XxVOY9SxbVdxen05U1/BkuL +9eQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc: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=xvLTNFWlMvg+HY64rDNvkGcJ0i15FJbhkNuqG+SNYeY=; b=pQJhH6zSdg+XjD2uC+xWt1WDhMyPmhSdAto7c4Z9EZxLk8QjsohRMB35TjKLGX9ek6 9GaCfOv3S6pkjy8x7eHlIW9/JoonpDhzZHPnhd7JEpJdFaZ8H0xfFxXof73hogcQoPlq vAMbbZNNQiD6vUyd+N6OABx4DV+a1qxHlEAoIWd34PqvifS3IvVh/7sU0kYjMd82uap4 45IOypTmHwZlgP7A+KjRKTzdO5dPXQgaDc3z2vyfkpiDuiOgMGMiGEx9b3t2S+BElqyN E0iKYLR2mlh71HJpRDCCoEJuMzKSPb3u8Zt4lVk2SI66GmMkTOqstA23GsnZuBEWx0UF 3miw== X-Gm-Message-State: ACrzQf0CzdsjFOhMrXEJKjQxgt1e0dQJQI6xeQkaCCdaknuyRbpbxX69 LRpl6vZqXFdfWknV/OcDzu74ppZ0JJTOY2KM+Yntcau3 X-Google-Smtp-Source: AMsMyM76XBbFP4MucxR3O/X7qgIcby/2KNacvG9DPSWdjVZ5Su8itkXVYMYmYNK1e6Pc5jPI/8NFVH1usZpe7/o5WnA= X-Received: by 2002:a02:a883:0:b0:347:c2ed:9ff with SMTP id l3-20020a02a883000000b00347c2ed09ffmr6161763jam.217.1665295148664; Sat, 08 Oct 2022 22:59:08 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 References: <20220922180626.GB79310@darkbeer.org> <20220924070708.GA48911@darkbeer.org> In-Reply-To: From: Kevin Oberman Date: Sat, 8 Oct 2022 22:58:52 -0700 Message-ID: Subject: Re: Disabling CPUs To: Ian Smith Cc: questions@freebsd.org Content-Type: multipart/alternative; boundary="000000000000c8499105ea93bda3" X-Rspamd-Queue-Id: 4MlWZk29fzz45Nv X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=eB7VW61Q; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::d29 as permitted sender) smtp.mailfrom=kob6558@gmail.com X-Spamd-Result: default: False [-2.39 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.99)[-0.985]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; NEURAL_SPAM_SHORT(0.29)[0.290]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::d29:from]; ARC_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; MLMMJ_DEST(0.00)[questions@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N --000000000000c8499105ea93bda3 Content-Type: text/plain; charset="UTF-8" N.B. Typo alert. I entered 1.1W for idle on 4 P threads. That should be 10.1. Very sorry for the error. 1.1W was really unbelievable, and I should have realized it. I collected the 4 threads numbers and recorded them much earlier then I switched to 8 E threads and created my reply. On Sat, Oct 8, 2022 at 6:28 PM Kevin Oberman wrote: > On Sat, Oct 8, 2022 at 5:54 PM Kevin Oberman wrote: > >> On Fri, Oct 7, 2022 at 9:56 AM Ian Smith wrote: >> >>> On 7 October 2022 2:05:32 pm AEDT, Kevin Oberman >>> wrote: >>> >>> [...] >>> >>> > I've been silent while waiting for the additional memory since I >>> > could not >>> > do any real work with only 8G. It finally arrived and I installed it >>> > yesterday. I'm very happy to say that my VirtualBox VMs seem to now >>> > be >>> > working correctly. I've done limited testing, but seen no problems to >>> > this >>> > point. Much better than an instant system panic when a VM finished >>> > loading. >>> > >>> > On the plus side, with "cpuset -s 1 -l 0-3", things seem reasonably >>> > stable. >>> > That means no crashes with many hours of use and a lot of >>> > compilations. >>> > With only 4 cores, it's not a fast as I had hoped, but I will be >>> > benchmarking soon. >>> >>> Hi Kevin, three questions if I may: >>> >>> I may have missed it, but did you wind up testing sched_ULE vs 4BSD? >>> >> >> cpuset(8) only works with ULE, so that is what I am running. So far I >> have not seen the interactivity issues that caused me to move to 4BSD over >> a decade ago. >> >> >>> Is that 4 cores including HT, or not? >>> >> >> Yes, 2 cores and 4 threads. Sorry to have failed to make that clear. My >> CPU has 2 P cores and 8 E cores. It has never crashed when running the 2 P >> cores, but I had one crash running the 8 E cores. Now that I have a >> stable system, I may try switching back to just the E cores as they seem >> to provide almost double the performance of the 2 P cores. Oddly, while >> using rsync to move a big batch of files from my backup disk to the new >> system after cpuset, I saw 0-3 busy, as I would expect, but one E core was >> running at about 30% the entire time, as well. I have no idea why. >> >>> >>> And how much power does your new Thinkpad T16 use on battery, say, at >>> idle and 'fairly busy' (acpiconf -i0) ? >>> >> >> With the 2 P cores I see about 1.1W idle. Wow! While compiling Firefox >> (all threads running at over 95%), I see about 25.3W. With a 52500 mWh >> battery, it will last a long time. >> With the 9 E cores I see about 10.4W idle. Wow, the other way. While >> compiling Firefox, I saw a momentary spike of 35W, but it varied between >> 20.5 and 27.8 W with occasional hits up to 31 W. The E core power >> consumption seems far more inconsistent thaa the P cores. compile time with >> P cores was 1:29 while it was only :50 with the 8 E cores. >> >> In both cases I had my Mate desktop running. >> >> The L15 was a piece of junk where I learned my lesson about budget >> systems. The ABS case started cracking at both hinges after about a year >> of use. That was after about 9 months of trying to get it working properly >> after Lenovo had replaced the motherboard and the disk. and, finally, the >> keyboard. I think the MB was fine, but was the obvious suspect for system >> lock-ups in POST. Took my a while to track it down to the keyboard and the >> tech who swapped it out didn't believe that the keyboard was the problem >> but agreed to humor me. As a result, by the time the case started cracking, >> the warranty had expired. If I had been willing to give up the TrackPoint, >> I would have bought a non-Lenovo/IBM for the first time ever. >> >> The T16 is built like a T series with a metal frame and feels solid. My >> T16 is all SSD. Yes, it's heavier. The L15 flexed noticeably with no frame, >> just the MB, battery, and disk attached to the ABS case. >> >> cheers, Ian >>> >> Sigh. Less than 5 minutes after I sent my reply, the "all E core" system > panicked. The usual vfs/ufs crash in ufs_lookup_ino. I'm back to all P > core" as that has never cashed. So far I have seen no activity on my ticket. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000c8499105ea93bda3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
N.B. Typo alert. I entered 1.1W for idle on=C2= =A0 4 P threads. That should be 10.1. Very sorry for the error.

1.1W was really unbelievable, and I should have rea= lized it. I collected the 4 threads numbers and recorded them much earlier = then I switched to 8 E threads and created my reply.

On Sat, Oct 8= , 2022 at 6:28 PM Kevin Oberman <= rkoberman@gmail.com> wrote:
On Sat, Oct = 8, 2022 at 5:54 PM Kevin Oberman <rkoberman@gmail.com> wrote:
On Fri, Oct 7, 2022 at 9:56 AM Ian Smith <smithi@nimnet.asn.au> wr= ote:
On 7 October 2022 2:05:32 pm AEDT, Kevin Oberman <= rkoberman@gmail.co= m> wrote:

[...]

=C2=A0> I've been silent while waiting for the additional memory sin= ce I
=C2=A0> could not
=C2=A0> do any real work with only 8G. It finally arrived and I installe= d it
=C2=A0> yesterday. I'm very happy to say that my VirtualBox VMs seem= to now
=C2=A0> be
=C2=A0> working correctly. I've done limited testing, but seen no pr= oblems to
=C2=A0> this
=C2=A0> point. Much better than an instant system panic when a VM finish= ed
=C2=A0> loading.
=C2=A0>
=C2=A0> On the plus side, with "cpuset -s 1 -l 0-3", things se= em reasonably
=C2=A0> stable.
=C2=A0> That means no crashes with many hours of use and a lot of
=C2=A0> compilations.
=C2=A0> With only 4 cores, it's not a fast as I had hoped, but I wil= l be
=C2=A0> benchmarking soon.

Hi Kevin, three questions if I may:

I may have missed it, but did you wind up testing sched_ULE vs 4BSD?
=C2=A0
cpuset(8) only works with ULE, s= o that is what I am running. So far I have not seen the interactivity issue= s that caused me to move to 4BSD over a decade ago.=C2=A0
<= div>=C2=A0
Is that 4 cores including HT, or not?
=C2=A0
Yes, 2 cores and 4 threads. Sorry to have failed to make that c= lear. My CPU has 2 P cores and 8 E cores. It has never crashed=C2=A0 when r= unning the 2 P cores, but I had one crash running the 8 E cores.=C2= =A0Now that I have a stable system, I may try switching back to = just the E cores as they=C2=A0 seem to provide almost double the performanc= e of the 2 P cores. Oddly, while using rsync to move a big batch of files f= rom my backup disk to the new system after cpuset, I saw 0-3 busy, as I wou= ld expect, but one E core was running at about 30% the entire time, as well= . I have no idea why.

And how much power does your new Thinkpad T16 use on battery, say, at idle = and 'fairly busy' (acpiconf -i0) ?

<= div style=3D"font-family:tahoma,sans-serif;font-size:small">With=C2=A0 the = 2 P cores I see about 1.1W idle. Wow! While compiling Firefox (all=C2=A0 th= reads running at over 95%), I see about 25.3W. With a 52500 mWh battery, it= will last a long time.
With the 9 E cores I see about 10.4W idle. Wow, the other wa= y. While compiling Firefox, I saw a momentary spike of 35W, but it varied b= etween 20.5 and 27.8 W with occasional hits up to 31 W. The E core power co= nsumption seems far more inconsistent thaa the P cores. compile time with P= cores was 1:29 while it was only :50 with the 8 E cores.

In both cases I had my M= ate desktop running.

The L15 was a piece of junk where I learned my lesson about bud= get systems.=C2=A0 The ABS case started cracking at both hinges after about= a year of use. That was after about 9 months of trying to get it working p= roperly after Lenovo had replaced the motherboard and the disk. and, finall= y, the keyboard. I think the MB was fine, but was the obvious suspect for s= ystem lock-ups in POST. Took my a while to track it down to the keyboard an= d the tech who swapped it out didn't believe that the keyboard was the = problem but agreed to humor me. As a result, by the time the case started c= racking, the warranty had expired. If I had been willing to give up the Tra= ckPoint, I would have bought a non-Lenovo/IBM for the first time ever.

The T16 is built = like a T series with a metal frame and feels solid. My T16 is all SSD. Yes= , it's heavier. The L15 flexed noticeably with no frame, just the MB, b= attery, and disk attached to the ABS case.

cheers, Ian
Sigh. Less than 5 min= utes after I sent my reply, the=C2=A0"all E core&quo= t; system panicked. The usual vfs/ufs crash in ufs_lookup_ino. I'm back= to all P core" as that has never cashed. So far I have seen no activi= ty on my ticket.
--
Kevi= n Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com


--
--000000000000c8499105ea93bda3--