• [gentoo-user] emerge times blown out

    From Adam Carter@21:1/5 to All on Sat Feb 18 01:50:02 2023
    I have three systems (all ~arch) and the emerge times have blown out on all
    of them across all packages. Worst example appears to be;

    Fri Dec 23 13:11:44 2022 >>> net-libs/webkit-gtk-2.38.3-r410
    merge time: 37 minutes and 8 seconds.

    Fri Dec 23 13:43:08 2022 >>> net-libs/webkit-gtk-2.38.3
    merge time: 31 minutes and 24 seconds.

    Sat Feb 4 21:16:40 2023 >>> net-libs/webkit-gtk-2.38.4-r410
    merge time: 6 hours, 53 minutes and 28 seconds.

    Sun Feb 5 04:17:12 2023 >>> net-libs/webkit-gtk-2.38.4
    merge time: 7 hours and 32 seconds.

    Is anyone else seeing this?

    <div dir="ltr"><div>I have three systems (all ~arch) and the emerge times have blown out on all of them across all packages. Worst example appears to be;</div><div><br></div><div>    Fri Dec 23 13:11:44 2022 &gt;&gt;&gt; net-libs/webkit-gtk-2.38.3-r410<
           merge time: 37 minutes and 8 seconds.<br><br>     Fri Dec 23 13:43:08 2022 &gt;&gt;&gt; net-libs/webkit-gtk-2.38.3<br>       merge time: 31 minutes and 24 seconds.<br><br>     Sat Feb  4 21:16:40 2023 &gt;&gt;&gt; net-libs/webkit-
    gtk-2.38.4-r410<br>       merge time: 6 hours, 53 minutes and 28 seconds.<br><br>     Sun Feb  5 04:17:12 2023 &gt;&gt;&gt; net-libs/webkit-gtk-2.38.4<br>       merge time: 7 hours and 32 seconds.</div><div><br></div><div>Is anyone else
    seeing this?<br></div></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dale@21:1/5 to Adam Carter on Sat Feb 18 02:40:01 2023
    Adam Carter wrote:
    I have three systems (all ~arch) and the emerge times have blown out
    on all of them across all packages. Worst example appears to be;

        Fri Dec 23 13:11:44 2022 >>> net-libs/webkit-gtk-2.38.3-r410
           merge time: 37 minutes and 8 seconds.

         Fri Dec 23 13:43:08 2022 >>> net-libs/webkit-gtk-2.38.3
           merge time: 31 minutes and 24 seconds.

         Sat Feb  4 21:16:40 2023 >>> net-libs/webkit-gtk-2.38.4-r410
           merge time: 6 hours, 53 minutes and 28 seconds.

         Sun Feb  5 04:17:12 2023 >>> net-libs/webkit-gtk-2.38.4
           merge time: 7 hours and 32 seconds.

    Is anyone else seeing this?


    A lot of this will obviously depend on CPU speed, number of
    cores/threads, amount of memory and also, is it compiling on its own or
    are other packages also being compiled and taking up CPU time or other
    things using CPU time as well.  Here, AMD CPU at 4GHz with 8 cores. 
    32GBs of memory and most packages built on tmpfs, except large
    packages.  This is a recent few examples. 


         Sat Aug  6 06:34:31 2022 >>> net-libs/webkit-gtk-2.36.5-r1        merge time: 1 hour, 39 minutes and 13 seconds.

         Sun Aug 21 16:04:23 2022 >>> net-libs/webkit-gtk-2.36.6
           merge time: 3 hours, 41 minutes and 44 seconds.

         Sat Sep  3 22:29:36 2022 >>> net-libs/webkit-gtk-2.36.7
           merge time: 2 hours, 41 minutes and 7 seconds.



    I left out binary emerges and such.  Oldest at top, newest at bottom.  I suspect for the middle and most likely the bottom one, there was another package compiling as well.  It's possible the top one was either on its
    own part or all of the time. 

    It's really hard to compare these things.  Even if our rigs are close in speed/power/whatever, there can still be a lot of things that affect the compile time.  I run KDE, watch TV from computer, have torrent software
    that runs basically 24/7 plus other stuff running.  If you for example
    use Fluxbox and have little else running, even with the same CPU and
    memory, compile times will vary. 

    Does that info help? 

    Dale

    :-)  :-) 

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dale@21:1/5 to Adam Carter on Sat Feb 18 08:40:01 2023
    This is a multi-part message in MIME format.
    Adam Carter wrote:

    Does that info help? 


    My reason for asking is that i'm seeing this across multiple systems,
    2 AMD, 1 Intel, who's configuration hasn't really changed and while
    there is some variance there has been a step change late December /
    early January. Another example

        Sat Nov 26 14:34:50 2022 >>> sys-apps/systemd-252.2
           merge time: 2 minutes and 19 seconds.

         Sat Dec 10 20:59:29 2022 >>> sys-apps/systemd-252.3
           merge time: 1 minute and 54 seconds.

         Wed Dec 14 13:56:52 2022 >>> sys-apps/systemd-252.3
           merge time: 2 minutes and 56 seconds.

         Wed Dec 21 20:08:36 2022 >>> sys-apps/systemd-252.4
           merge time: 3 minutes and 7 seconds.

         Tue Jan  3 22:29:43 2023 >>> sys-apps/systemd-252.4
           merge time: 12 minutes and 42 seconds.

         Thu Jan 12 14:56:32 2023 >>> sys-apps/systemd-252.4-r1
           merge time: 22 minutes and 12 seconds.

         Sat Jan 21 12:00:06 2023 >>> sys-apps/systemd-252.4-r1
           merge time: 12 minutes and 3 seconds.

         Mon Jan 30 15:41:44 2023 >>> sys-apps/systemd-252.5
           merge time: 21 minutes and 45 seconds.

         Fri Feb 17 21:18:21 2023 >>> sys-apps/systemd-252.6
           merge time: 22 minutes and 18 seconds.


    The ones I listed before also jumped in compile times.  As I said tho, I
    don't know if other things compiling affected that time.  Still, it does
    seem to have increased but I remember when I was on my old single core
    rig with just a few GBs of memory.  As time goes by, software gets
    bigger therefore takes longer to compile.  Yours from the 4th to the 6th
    in the list sure does increase.  That's 8 to 10 times longer roughly. 
    That's a large difference.  A true test, emerge something interesting
    all by itself.  See what it comes closest to, the old times or the newer
    and longer times. 

    I suspect this is changes in features of software and could even be
    related to gcc or some other tool compiling uses.  It is a interesting
    jump.  I don't think you are alone in this.  Maybe someone else will
    post their info.  For those interested, genlop -t <package name> is how
    to get this info. 

    BTW, I don't use systemd so I can't list mine.  ;-)

    Dale

    :-)  :-)

    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    </head>
    <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Adam Carter wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:CAC=wYCGhmV8eagrVSD_Zht77Nrr8fb6D4k=3w0jHwREDD6zpoA@mail.gmail.com">
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    <div dir="ltr">
    <div class="gmail_quote">
    <blockquote class="gmail_quote" style="margin:0px 0px 0px
    0.8ex;border-left:1px solid
    rgb(204,204,204);padding-left:1ex">
    Does that info help? <br>
    <br>
    </blockquote>
    <div><br>
    </div>
    <div>My reason for asking is that i'm seeing this across
    multiple systems, 2 AMD, 1 Intel, who's configuration hasn't
    really changed and while there is some variance there has
    been a step change late December / early January. Another
    example</div>
    <div><br>
    </div>
    <div>    Sat Nov 26 14:34:50 2022 &gt;&gt;&gt;
    sys-apps/systemd-252.2<br>
           merge time: 2 minutes and 19 seconds.<br>
    <br>
         Sat Dec 10 20:59:29 2022 &gt;&gt;&gt;
    sys-apps/systemd-252.3<br>
           merge time: 1 minute and 54 seconds.<br>
    <br>
         Wed Dec 14 13:56:52 2022 &gt;&gt;&gt;
    sys-apps/systemd-252.3<br>
           merge time: 2 minutes and 56 seconds.<br>
    <br>
         Wed Dec 21 20:08:36 2022 &gt;&gt;&gt;
    sys-apps/systemd-252.4<br>
           merge time: 3 minutes and 7 seconds.<br>
    <br>
         Tue Jan  3 22:29:43 2023 &gt;&gt;&gt;
    sys-apps/systemd-252.4<br>
           merge time: 12 minutes and 42 seconds.<br>
    <br>
         Thu Jan 12 14:56:32 2023 &gt;&gt;&gt;
    sys-apps/systemd-252.4-r1<br>
           merge time: 22 minutes and 12 seconds.<br>
    <br>
         Sat Jan 21 12:00:06 2023 &gt;&gt;&gt;
    sys-apps/systemd-252.4-r1<br>
           merge time: 12 minutes and 3 seconds.<br>
    <br>
         Mon Jan 30 15:41:44 2023 &gt;&gt;&gt;
    sys-apps/systemd-252.5<br>
           merge time: 21 minutes and 45 seconds.<br>
    <br>
         Fri Feb 17 21:18:21 2023 &gt;&gt;&gt;
    sys-apps/systemd-252.6<br>
           merge time: 22 minutes and 18 seconds.<br>
    </div>
    </div>
    </div>
    </blockquote>
    <br>
    <br>
    The ones I listed before also jumped in compile times.  As I said
    tho, I don't know if other things compiling affected that time. 
    Still, it does seem to have increased but I remember when I was on
    my old single core rig with just a few GBs of memory.  As time goes
    by, software gets bigger therefore takes longer to compile.  Yours
    from the 4th to the 6th in the list sure does increase.  That's 8 to
    10 times longer roughly.  That's a large difference.  A true test,
    emerge something interesting all by itself.  See what it comes
    closest to, the old times or the newer and longer times.  <br>
    <br>
    I suspect this is changes in features of software and could even be
    related to gcc or some other tool compiling uses.  It is a
    interesting jump.  I don't think you are alone in this.  Maybe
    someone else will post their info.  For those interested, genlop -t
    &lt;package name&gt; is how to get this info.  <br>
    <br>
    BTW, I don't use systemd so I can't list mine.  ;-) <br>
    <br>
    Dale <br>
    <br>
    :-)  :-) <br>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam Carter@21:1/5 to All on Sat Feb 18 08:20:01 2023

    Does that info help?


    My reason for asking is that i'm seeing this across multiple systems, 2
    AMD, 1 Intel, who's configuration hasn't really changed and while there is
    some variance there has been a step change late December / early January. Another example

    Sat Nov 26 14:34:50 2022 >>> sys-apps/systemd-252.2
    merge time: 2 minutes and 19 seconds.

    Sat Dec 10 20:59:29 2022 >>> sys-apps/systemd-252.3
    merge time: 1 minute and 54 seconds.

    Wed Dec 14 13:56:52 2022 >>> sys-apps/systemd-252.3
    merge time: 2 minutes and 56 seconds.

    Wed Dec 21 20:08:36 2022 >>> sys-apps/systemd-252.4
    merge time: 3 minutes and 7 seconds.

    Tue Jan 3 22:29:43 2023 >>> sys-apps/systemd-252.4
    merge time: 12 minutes and 42 seconds.

    Thu Jan 12 14:56:32 2023 >>> sys-apps/systemd-252.4-r1
    merge time: 22 minutes and 12 seconds.

    Sat Jan 21 12:00:06 2023 >>> sys-apps/systemd-252.4-r1
    merge time: 12 minutes and 3 seconds.

    Mon Jan 30 15:41:44 2023 >>> sys-apps/systemd-252.5
    merge time: 21 minutes and 45 seconds.

    Fri Feb 17 21:18:21 2023 >>> sys-apps/systemd-252.6
    merge time: 22 minutes and 18 seconds.

    <div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
    Does that info help? <br>
    <br></blockquote><div><br></div><div>My reason for asking is that i&#39;m seeing this across multiple systems, 2 AMD, 1 Intel, who&#39;s configuration hasn&#39;t really changed and while there is some variance there has been a step change late December /
    early January. Another example</div><div><br></div><div>    Sat Nov 26 14:34:50 2022 &gt;&gt;&gt; sys-apps/systemd-252.2<br>       merge time: 2 minutes and 19 seconds.<br><br>     Sat Dec 10 20:59:29 2022 &gt;&gt;&gt; sys-apps/systemd-252.3<br>Â
           merge time: 1 minute and 54 seconds.<br><br>     Wed Dec 14 13:56:52 2022 &gt;&gt;&gt; sys-apps/systemd-252.3<br>       merge time: 2 minutes and 56 seconds.<br><br>     Wed Dec 21 20:08:36 2022 &gt;&gt;&gt; sys-apps/systemd-252.4<br>Â
           merge time: 3 minutes and 7 seconds.<br><br>     Tue Jan  3 22:29:43 2023 &gt;&gt;&gt; sys-apps/systemd-252.4<br>       merge time: 12 minutes and 42 seconds.<br><br>     Thu Jan 12 14:56:32 2023 &gt;&gt;&gt; sys-apps/systemd-252.4-
    r1<br>       merge time: 22 minutes and 12 seconds.<br><br>     Sat Jan 21 12:00:06 2023 &gt;&gt;&gt; sys-apps/systemd-252.4-r1<br>       merge time: 12 minutes and 3 seconds.<br><br>     Mon Jan 30 15:41:44 2023 &gt;&gt;&gt; sys-apps/
    systemd-252.5<br>       merge time: 21 minutes and 45 seconds.<br><br>     Fri Feb 17 21:18:21 2023 &gt;&gt;&gt; sys-apps/systemd-252.6<br>       merge time: 22 minutes and 18 seconds.<br></div></div></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan J. Wylie@21:1/5 to Adam Carter on Sat Feb 18 09:30:01 2023
    Adam Carter <adamcarter3@gmail.com> writes:

    My reason for asking is that i'm seeing this across multiple systems, 2
    AMD, 1 Intel, who's configuration hasn't really changed and while there is some variance there has been a step change late December / early January. Another example

    Sat Nov 26 14:34:50 2022 >>> sys-apps/systemd-252.2
    merge time: 2 minutes and 19 seconds.

    Sat Dec 10 20:59:29 2022 >>> sys-apps/systemd-252.3
    merge time: 1 minute and 54 seconds.

    Wed Dec 14 13:56:52 2022 >>> sys-apps/systemd-252.3
    merge time: 2 minutes and 56 seconds.

    Wed Dec 21 20:08:36 2022 >>> sys-apps/systemd-252.4
    merge time: 3 minutes and 7 seconds.

    Tue Jan 3 22:29:43 2023 >>> sys-apps/systemd-252.4
    merge time: 12 minutes and 42 seconds.

    Thu Jan 12 14:56:32 2023 >>> sys-apps/systemd-252.4-r1
    merge time: 22 minutes and 12 seconds.

    Sat Jan 21 12:00:06 2023 >>> sys-apps/systemd-252.4-r1
    merge time: 12 minutes and 3 seconds.

    Mon Jan 30 15:41:44 2023 >>> sys-apps/systemd-252.5
    merge time: 21 minutes and 45 seconds.

    Fri Feb 17 21:18:21 2023 >>> sys-apps/systemd-252.6
    merge time: 22 minutes and 18 seconds.

    All my three systems are fine

    AMD FX(tm)-8350 Eight-Core Processor, 16GiB

    Sun Oct 2 13:07:33 2022 >>> sys-apps/systemd-251.4
    merge time: 3 minutes and 35 seconds.

    Fri Nov 25 08:06:10 2022 >>> sys-apps/systemd-251.7
    merge time: 3 minutes and 24 seconds.

    Sat Dec 10 10:11:16 2022 >>> sys-apps/systemd-251.8
    merge time: 3 minutes and 19 seconds.

    Tue Jan 3 08:43:49 2023 >>> sys-apps/systemd-252.4
    merge time: 3 minutes and 22 seconds.

    Sat Jan 28 06:28:16 2023 >>> sys-apps/systemd-252.4-r1
    merge time: 5 minutes and 24 seconds.

    AMD FX(tm)-4300 Quad-Core Processor, 16GiB

    Sun Oct 2 13:42:48 2022 >>> sys-apps/systemd-251.4
    merge time: 5 minutes and 32 seconds.

    Fri Nov 25 08:11:27 2022 >>> sys-apps/systemd-251.7
    merge time: 5 minutes and 40 seconds.

    Sat Dec 10 12:31:38 2022 >>> sys-apps/systemd-251.8
    merge time: 5 minutes and 36 seconds.

    Tue Jan 3 08:47:13 2023 >>> sys-apps/systemd-252.4
    merge time: 5 minutes and 36 seconds.

    Sat Jan 28 06:28:27 2023 >>> sys-apps/systemd-252.4-r1
    merge time: 6 minutes and 17 seconds.

    Intel(R) Atom(TM) CPU N2800 @ 1.86GHz, 4GiB, not systemd

    Wed Sep 28 08:32:50 2022 >>> net-dns/bind-9.16.33
    merge time: 15 minutes and 28 seconds.

    Fri Jan 20 07:50:41 2023 >>> net-dns/bind-9.16.36
    merge time: 16 minutes and 23 seconds.

    Thu Feb 16 07:33:46 2023 >>> net-dns/bind-9.16.37
    merge time: 17 minutes and 9 seconds.

    --
    Alan J. Wylie https://www.wylie.me.uk/

    Dance like no-one's watching. / Encrypt like everyone is.
    Security is inversely proportional to convenience

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stefan Schmiedl@21:1/5 to All on Sat Feb 18 13:20:01 2023
    Samstag, 18. Februar 2023 01:49:
     
    I have three systems (all ~arch) and the emerge times have blown out on all of them across all packages. Worst example appears to be;

        Fri Dec 23 13:11:44 2022 >>> net-libs/webkit-gtk-2.38.3-r410
           merge time: 37 minutes and 8 seconds.

         Fri Dec 23 13:43:08 2022 >>> net-libs/webkit-gtk-2.38.3
           merge time: 31 minutes and 24 seconds.

         Sat Feb  4 21:16:40 2023 >>> net-libs/webkit-gtk-2.38.4-r410
           merge time: 6 hours, 53 minutes and 28 seconds.

         Sun Feb  5 04:17:12 2023 >>> net-libs/webkit-gtk-2.38.4
           merge time: 7 hours and 32 seconds.

    Is anyone else seeing this?

    When I had something like this about two years ago, the culprit was me
    setting the cpufreq thingie in the kernel config to powersave or whatever
    it's called ... running emerge with 800 MHz instead of 3.2 GHz produced
    effects similar to yours.

    s. 
     

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Grant Edwards@21:1/5 to Stefan Schmiedl on Sat Feb 18 19:10:01 2023
    On 2023-02-18, Stefan Schmiedl <s@xss.de> wrote:
    Samstag, 18. Februar 2023 01:49:
     
    I have three systems (all ~arch) and the emerge times have blown out on all of them across all packages. Worst example appears to be;

        Fri Dec 23 13:11:44 2022 >>> net-libs/webkit-gtk-2.38.3-r410
           merge time: 37 minutes and 8 seconds.

         Fri Dec 23 13:43:08 2022 >>> net-libs/webkit-gtk-2.38.3
           merge time: 31 minutes and 24 seconds.

         Sat Feb  4 21:16:40 2023 >>> net-libs/webkit-gtk-2.38.4-r410
           merge time: 6 hours, 53 minutes and 28 seconds.

         Sun Feb  5 04:17:12 2023 >>> net-libs/webkit-gtk-2.38.4
           merge time: 7 hours and 32 seconds.

    Is anyone else seeing this?

    When I had something like this about two years ago, the culprit was me setting the cpufreq thingie in the kernel config to powersave or whatever it's called ... running emerge with 800 MHz instead of 3.2 GHz produced effects similar to yours.

    The same thing happened to me recently. Somehow, I broke the load/temp
    based CPU clock scaling on one of my machines, and it suddenly took 4X
    as long to build things as my other machines. It was running at the
    lowest clock speed possible all the time. Unfortunately, I don't
    remember exactly what I did to fix it...

    --
    Grant

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stefan Schmiedl@21:1/5 to All on Sat Feb 18 19:20:01 2023

    Samstag, 18. Februar 2023 19:05:

     

    On 2023-02-18, Stefan Schmiedl <s@xss.de> wrote:

    Samstag, 18. Februar 2023 01:49:

    I have three systems (all ~arch) and the emerge times have blown out on all of them across all packages.

    When I had something like this about two years ago, the culprit was me >>setting the cpufreq thingie in the kernel config to powersave or whatever >>it's called ... running emerge with 800 MHz instead of 3.2 GHz produced >>effects similar to yours.


    The same thing happened to me recently. Somehow, I broke the load/temp
    based CPU clock scaling on one of my machines, and it suddenly took 4X
    as long to build things as my other machines. It was running at the
    lowest clock speed possible all the time. Unfortunately, I don't
    remember exactly what I did to fix it...


    CONFIG_CPU_FREQ_GOV_PERFORMANCE
    CONFIG_CPU_FREQ_GOV_POWERSAVE
    CONFIG_CPU_FREQ_GOV_USERSPACE
    CONFIG_CPU_FREQ_GOV_ONDEMAND
    CONFIG_CPU_FREQ_GOV_CONSERVATIVE
    CONFIG_CPU_FREQ_GOV_SCHEDUTIL

    Back when I finally found it, all of these were set to "n" but for POWERSAVE which was set to "y".
    I rebuilt the kernel to use ONDEMAND and things were back to normal.

    s.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam Carter@21:1/5 to All on Mon Feb 20 02:20:01 2023
    Thanks everyone for your suggestions. I've checked the frequencies of the
    cores and they are scaling properly:
    cpu MHz : 4024.653
    cpu MHz : 4024.678
    cpu MHz : 4024.639
    cpu MHz : 4024.605
    cpu MHz : 4024.643
    etc

    Will continue to pursue these lines of thought.

    <div dir="ltr"><div dir="ltr"><div>Thanks everyone for your suggestions. I&#39;ve checked the frequencies of the cores and they are scaling properly:</div><div>cpu MHz         : 4024.653<br>cpu MHz         : 4024.678<br>cpu MHz         : 4024.
    639<br>cpu MHz         : 4024.605<br></div><div>cpu MHz         : 4024.643</div><div>etc</div><div><br></div><div>Will continue to pursue these lines of thought.<br></div></div></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alexander Puchmayr@21:1/5 to All on Mon Feb 20 22:50:01 2023
    Am Samstag, 18. Februar 2023, 01:49:11 CET schrieb Adam Carter:
    I have three systems (all ~arch) and the emerge times have blown out on all of them across all packages. Worst example appears to be;

    Fri Dec 23 13:11:44 2022 >>> net-libs/webkit-gtk-2.38.3-r410
    merge time: 37 minutes and 8 seconds.

    Fri Dec 23 13:43:08 2022 >>> net-libs/webkit-gtk-2.38.3
    merge time: 31 minutes and 24 seconds.

    Sat Feb 4 21:16:40 2023 >>> net-libs/webkit-gtk-2.38.4-r410
    merge time: 6 hours, 53 minutes and 28 seconds.

    Sun Feb 5 04:17:12 2023 >>> net-libs/webkit-gtk-2.38.4
    merge time: 7 hours and 32 seconds.

    Is anyone else seeing this?

    Could it be that some kind of Spectre mitigation is active? I just read about some massive performance problems in Kernel 5.19+ on Skylake CPUs. Stable gentoo kernel was upgraded to 6.1 recently, which could also be affected by this problem.
    See https://lkml.iu.edu/hypermail/linux/kernel/2209.1/02248.html

    Try turning the mitigations off or revert to a 5.15.x kernel.

    Alex

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam Carter@21:1/5 to All on Tue Feb 21 21:50:01 2023

    Could it be that some kind of Spectre mitigation is active? I just read
    about
    some massive performance problems in Kernel 5.19+ on Skylake CPUs. Stable gentoo kernel was upgraded to 6.1 recently, which could also be affected
    by
    this problem.
    See https://lkml.iu.edu/hypermail/linux/kernel/2209.1/02248.html

    Try turning the mitigations off or revert to a 5.15.x kernel.


    I have one skylake and its now running 6.2 with retbleed=stuff. The others
    are AMD.

    I will try 5.15.x. I have .configs from that time so it will rule kernel
    stuff in/out.

    <div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
    Could it be that some kind of Spectre mitigation is active? I just read about <br>
    some massive performance problems in Kernel 5.19+ on Skylake CPUs. Stable <br> gentoo kernel was upgraded to 6.1 recently, which could also be affected by <br>
    this problem.<br>
    See <a href="https://lkml.iu.edu/hypermail/linux/kernel/2209.1/02248.html" rel="noreferrer" target="_blank">https://lkml.iu.edu/hypermail/linux/kernel/2209.1/02248.html</a><br>

    Try turning the mitigations off or revert to a 5.15.x kernel.<br></blockquote><div><br></div><div>I have one skylake and its now running 6.2 with retbleed=stuff. The others are AMD.</div><div><br></div><div>I will try 5.15.x. I have .configs from that
    time so it will rule kernel stuff in/out.<br></div></div></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)