public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: CPU upgrade and LVM questions.
Date: Fri, 7 Dec 2018 00:22:43 +0200	[thread overview]
Message-ID: <puc7a6$lh3$1@blaine.gmane.org> (raw)
In-Reply-To: <8bf206fd-e1eb-83aa-55b2-a152421503ac@gmail.com>

On 06/12/2018 23:45, Dale wrote:
>>
>> You won't get anything close to double the speed. The extra cores will
>> mostly go unused, unless you use applications that make use of them.
>>
>> You will still get a speed up due to the newer CPU architecture and
>> the higher frequency.
> 
> What I was thinking about is something like when compiling and all the
> cores are used.  In other words, CPU is at max load.  Right now, I have
> only 4 cores.  New CPU doubles that and each core is faster as well.  As
> a example, Firefox takes about a hour to compile.  I was hopeful that
> would drop to 30 or 35 minutes or so.

Oh that. Yeah, there will be a 2x speedup when emerging packages 
(MAKEOPTS="-j8"). I was referring to application performance when using 
the machine. I don't consider package installation as "using the 
machine" :-)


>> The two speeds specify the lower and upper speeds, depending on how
>> many CPU cores are currently being under load, and also how much load
>> there is. You don't have to worry about it though. It's all automatic.
>> [...]
> 
> That's good to know.  That I was wondering about and couldn't find a
> clear answer on.  I didn't know if I needed to install something to
> manage that or what.

The kernel takes care of that. You should be able to observe the CPU's 
frequency and temperature in KSysGuard. Here's how it looks here:

   https://i.imgur.com/Xogy3h0.png

In that screenshot, the CPU has all 4 cores clocked down to 1.6GHz 
because they're all mostly idle. Once there's high CPU load, it will 
crank up the clocks towards 4GHz.

You need to add these sensors manually to KSysGuard though. But if you 
do, it's a good way to verify things are working as intended.



  reply	other threads:[~2018-12-06 22:22 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06  9:27 [gentoo-user] CPU upgrade and LVM questions Dale
2018-12-06 10:03 ` Neil Bothwick
2018-12-06 15:17   ` Dale
2018-12-06 16:51   ` J. Roeleveld
2018-12-06 18:36 ` Corbin Bird
2018-12-06 20:58   ` Dale
2018-12-06 21:24     ` Jack
2018-12-06 21:55       ` Dale
2018-12-07  1:06     ` Corbin Bird
2018-12-07  1:17       ` Dale
2018-12-07  5:10         ` Dale
2018-12-07  6:22           ` [gentoo-user] " Nikos Chantziaras
2018-12-07  7:30             ` Dale
2018-12-07 10:49               ` Alec Ten Harmsel
2018-12-07 23:47               ` Nikos Chantziaras
2018-12-07 23:59                 ` Dale
2018-12-09 18:23                 ` Taiidan
2018-12-09 18:57                   ` J. Roeleveld
2018-12-09 22:41                     ` Dale
2018-12-10 21:33                     ` Taiidan
2018-12-10 22:14                       ` Neil Bothwick
2018-12-10 22:54                         ` Dale
2018-12-11  2:00                           ` Taiidan
2018-12-11  8:49                             ` Neil Bothwick
2018-12-11  9:23                               ` Mick
2018-12-11 10:48                               ` Dale
2018-12-11 15:14                                 ` J. Roeleveld
2018-12-11 22:46                               ` Adam Carter
2018-12-11 23:56                                 ` Dale
2018-12-12  2:15                                   ` Adam Carter
2018-12-11 10:20                             ` Alan Mackenzie
2018-12-11 15:03                             ` J. Roeleveld
2018-12-07  8:47         ` [gentoo-user] " Neil Bothwick
2018-12-07  8:58           ` Dale
2018-12-06 21:02 ` [gentoo-user] " Nikos Chantziaras
2018-12-06 21:45   ` Dale
2018-12-06 22:22     ` Nikos Chantziaras [this message]
2018-12-06 23:23       ` Dale
2018-12-06 23:40         ` Nikos Chantziaras
2018-12-07  0:19           ` Dale
2018-12-07 10:01             ` Peter Humphrey
2018-12-07 12:41               ` Dale
2018-12-07 16:51                 ` Peter Humphrey
2018-12-08  1:01                   ` Dale
2018-12-08  2:51                     ` Nikos Chantziaras
2018-12-08  4:39                       ` Dale
2018-12-08  5:33                       ` David Haller
2018-12-08  5:45                         ` Dale
2018-12-08  6:00                         ` Nikos Chantziaras
2018-12-08  6:28                           ` David Haller
2018-12-08  4:23                 ` David Haller
2018-12-08  5:35                   ` Dale
2018-12-08  6:06                     ` David Haller
2018-12-08  5:38                   ` David Haller
2018-12-08  9:40                     ` Peter Humphrey
2018-12-08  9:50                       ` Peter Humphrey
2018-12-06 21:03 ` [gentoo-user] " Grant Taylor
2018-12-09 22:45   ` Dale
2018-12-10  1:35     ` Grant Taylor
2018-12-10  2:38       ` Dale
2018-12-10  3:37         ` Grant Taylor
2018-12-10  9:27         ` Neil Bothwick
2018-12-10 16:00           ` Dale
2018-12-08 17:49 ` Alexander Puchmayr
2018-12-08 18:23   ` Dale
2018-12-08 19:09     ` J. Roeleveld
2018-12-08 20:48       ` Dale
2018-12-11 10:41 ` Dale
2018-12-22 23:58 ` Dale

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='puc7a6$lh3$1@blaine.gmane.org' \
    --to=realnc@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