Date: Sat, 8 Oct 2022 22:58:52 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Ian Smith <smithi@nimnet.asn.au> Cc: questions@freebsd.org Subject: Re: Disabling CPUs Message-ID: <CAN6yY1vNDPasM33piQ2k5SqcgBSm6dqKsQxnyvbd8aFHV1EkrA@mail.gmail.com> In-Reply-To: <CAN6yY1taXYzsCcuX%2Bax1j%2BRmk%2BL5%2BG7AyWf_kaY9chh35N6N3A@mail.gmail.com> References: <CAN6yY1s=ds_=yWsEWtVfoXchD5XXqU5uPw6bdFNW%2BdaU6t491A@mail.gmail.com> <20220922180626.GB79310@darkbeer.org> <CAN6yY1voZgRRc8hCe_hVXusdoeQrt%2B=shO28FbiUNMzK_5F2hQ@mail.gmail.com> <20220924070708.GA48911@darkbeer.org> <CAN6yY1vTxGMAhXcKEd%2BqZbMtbo13yS%2Buk25gjES_K1KF=zz2EA@mail.gmail.com> <CAFYkXjk=uRSsfdp80PcomVrdTE6Zz4fgN99S2L=KG%2Bz7a-w6qg@mail.gmail.com> <CAN6yY1uMapVZ_V=JnoaMnd_c0GK4CUrQ37wTnXH1jFGVOiU6wQ@mail.gmail.com> <C8FB4F23-252D-49C4-A9D6-1ADDF793A6FE@nimnet.asn.au> <CAN6yY1uNfXjMxnxMdr1uLC5wZVLoWGfkzGN54AxW%2BZywF7NVbg@mail.gmail.com> <CAN6yY1taXYzsCcuX%2Bax1j%2BRmk%2BL5%2BG7AyWf_kaY9chh35N6N3A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <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> wrote: >> >>> On 7 October 2022 2:05:32 pm AEDT, Kevin Oberman <rkoberman@gmail.com> >>> 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 <div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:tahoma,s= ans-serif;font-size:small">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.</div><div c= lass=3D"gmail_default" style=3D"font-family:tahoma,sans-serif;font-size:sma= ll"><br></div><div class=3D"gmail_default" style=3D"font-family:tahoma,sans= -serif;font-size:small">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.<br></div></div><br><di= v class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Oct 8= , 2022 at 6:28 PM Kevin Oberman <<a href=3D"mailto:rkoberman@gmail.com">= rkoberman@gmail.com</a>> wrote:<br></div><blockquote class=3D"gmail_quot= e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)= ;padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_de= fault" style=3D"font-family:tahoma,sans-serif;font-size:small">On Sat, Oct = 8, 2022 at 5:54 PM Kevin Oberman <<a href=3D"mailto:rkoberman@gmail.com"= target=3D"_blank">rkoberman@gmail.com</a>> wrote:<br></div></div><div c= lass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px = 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div= dir=3D"ltr"><div dir=3D"ltr"><div style=3D"font-family:tahoma,sans-serif;f= ont-size:small">On Fri, Oct 7, 2022 at 9:56 AM Ian Smith <<a href=3D"mai= lto:smithi@nimnet.asn.au" target=3D"_blank">smithi@nimnet.asn.au</a>> wr= ote:<br></div></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_q= uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2= 04);padding-left:1ex">On 7 October 2022 2:05:32 pm AEDT, Kevin Oberman <= <a href=3D"mailto:rkoberman@gmail.com" target=3D"_blank">rkoberman@gmail.co= m</a>> wrote:<br> <br> [...]<br> <br> =C2=A0> I've been silent while waiting for the additional memory sin= ce I<br> =C2=A0> could not<br> =C2=A0> do any real work with only 8G. It finally arrived and I installe= d it<br> =C2=A0> yesterday. I'm very happy to say that my VirtualBox VMs seem= to now<br> =C2=A0> be<br> =C2=A0> working correctly. I've done limited testing, but seen no pr= oblems to<br> =C2=A0> this<br> =C2=A0> point. Much better than an instant system panic when a VM finish= ed<br> =C2=A0> loading.<br> =C2=A0> <br> =C2=A0> On the plus side, with "cpuset -s 1 -l 0-3", things se= em reasonably<br> =C2=A0> stable.<br> =C2=A0> That means no crashes with many hours of use and a lot of<br> =C2=A0> compilations.<br> =C2=A0> With only 4 cores, it's not a fast as I had hoped, but I wil= l be<br> =C2=A0> benchmarking soon.<br> <br> Hi Kevin, three questions if I may:<br> <br> I may have missed it, but did you wind up testing sched_ULE vs 4BSD?<br></b= lockquote><div>=C2=A0</div><div><span class=3D"gmail_default" style=3D"font= -family:tahoma,sans-serif;font-size:small">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.</span>=C2=A0<br></div><= div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0= px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> Is that 4 cores including HT, or not?<br></blockquote><div>=C2=A0</div><div= ><span class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif;font-= size:small">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.</span>=C2= =A0<span class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif;fon= t-size:small">Now 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.<br></span></div><blockquote class=3D"gmail_quote" sty= le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi= ng-left:1ex"> <br> And how much power does your new Thinkpad T16 use on battery, say, at idle = and 'fairly busy' (acpiconf -i0) ?<br></blockquote><div><br></div><= 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.</div><div style=3D"font-family:tahoma,sans-serif;fo= nt-size:small">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.<br></div><div sty= le=3D"font-family:tahoma,sans-serif;font-size:small"><br></div><div style= =3D"font-family:tahoma,sans-serif;font-size:small">In both cases I had my M= ate desktop running.<br></div><div style=3D"font-family:tahoma,sans-serif;f= ont-size:small"><br></div><div style=3D"font-family:tahoma,sans-serif;font-= size:small">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.</div= ><div style=3D"font-family:tahoma,sans-serif;font-size:small"><br></div><di= v style=3D"font-family:tahoma,sans-serif;font-size:small">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.</div><div style=3D"font-family:t= ahoma,sans-serif;font-size:small"><br></div><blockquote class=3D"gmail_quot= e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)= ;padding-left:1ex"><span class=3D"gmail_default" style=3D"font-family:tahom= a,sans-serif;font-size:small"></span> cheers, Ian<br> </blockquote></div></div></blockquote><div><span class=3D"gmail_default" st= yle=3D"font-family:tahoma,sans-serif;font-size:small">Sigh. Less than 5 min= utes after I sent my reply, the</span>=C2=A0<span class=3D"gmail_default" s= tyle=3D"font-family:tahoma,sans-serif;font-size:small">"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.<br></span></div></div>-- <br><div dir=3D"ltr"><div dir=3D"= ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr">Kevi= n Oberman, Part time kid herder and retired Network Engineer<br>E-mail: <a = href=3D"mailto:rkoberman@gmail.com" target=3D"_blank">rkoberman@gmail.com</= a><br></div><div>PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683<= /div></div></div></div></div></div></div></div></div> </blockquote></div><br clear=3D"all"><br>-- <br><div dir=3D"ltr" class=3D"g= mail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr= "><div><div dir=3D"ltr">Kevin Oberman, Part time kid herder and retired Net= work Engineer<br>E-mail: <a href=3D"mailto:rkoberman@gmail.com" target=3D"_= blank">rkoberman@gmail.com</a><br></div><div>PGP Fingerprint: D03FB98AFA78E= 3B78C1694B318AB39EF1B055683</div></div></div></div></div></div></div></div> --000000000000c8499105ea93bda3--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1vNDPasM33piQ2k5SqcgBSm6dqKsQxnyvbd8aFHV1EkrA>