From: Andre McCurdy <armccurdy@gmail.com> To: Ryan Meulenkamp <Ryan.Meulenkamp@nedap.com> Cc: Yocto discussion list <yocto@yoctoproject.org>, OE Core mailing list <openembedded-core@lists.openembedded.org> Subject: Re: CPU Load Date: Wed, 28 Mar 2018 18:24:22 -0700 [thread overview] Message-ID: <CAJ86T=WE6khW6vfL2_z3HdXjB-pxSSaTAb=Fz-NSczhTGxV=HQ@mail.gmail.com> (raw) In-Reply-To: <12dbba60-2346-0020-64c8-db2dac948684@nedap.com> On Tue, Mar 27, 2018 at 4:44 AM, Ryan Meulenkamp <Ryan.Meulenkamp@nedap.com> wrote: > Hi y'all, > > I have some questions about CPU load and performance, but first some > background information. > > We have small embedded system running an openembedded classic (Angström) > distro. Now to get ourselves up-to-date we started working on a new > iteration of the OS based on openembedded core and Yocto. It is nearly > finished now, if it weren't for one problem: The CPU load (/proc/loadavg) of > the core/yocto based OS is more than double that of the classic/Angström OS. > > So the way I see it this could be caused by a number of factors: > > - loadavg's calculation changed > - certain newer versions of applications run heavier > - The kernel itself is heavier (we upgraded from 2.6.35.14+ to 4.9.28+) > - Possibly caused by some configs > - ... > > My question: is there something that changed since OE-classic that you know > could be the cause of this? If not, how would I go about finding the cause? > I don't think the top command is sufficient for this, because it's precision > is such that many processes' CPU usage just become 0%. You don't say what the CPU doubled from or too. 1% to 2%, or 50% to 100% ? Unless the absolute increase is very small, you can probably ignore the processes which top reports as 0%. Does the new build have any significant processes running which weren't there in the old build? Or is it the same basic set of apps running in each? > Also, both top and > htop cause huge cpu loads themselves. > > Any tips and tricks would be welcome! > > Thanks in advance! > > Ryan > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto
WARNING: multiple messages have this Message-ID (diff)
From: Andre McCurdy <armccurdy@gmail.com> To: Ryan Meulenkamp <Ryan.Meulenkamp@nedap.com> Cc: Yocto discussion list <yocto@yoctoproject.org>, OE Core mailing list <openembedded-core@lists.openembedded.org> Subject: Re: [yocto] CPU Load Date: Wed, 28 Mar 2018 18:24:22 -0700 [thread overview] Message-ID: <CAJ86T=WE6khW6vfL2_z3HdXjB-pxSSaTAb=Fz-NSczhTGxV=HQ@mail.gmail.com> (raw) In-Reply-To: <12dbba60-2346-0020-64c8-db2dac948684@nedap.com> On Tue, Mar 27, 2018 at 4:44 AM, Ryan Meulenkamp <Ryan.Meulenkamp@nedap.com> wrote: > Hi y'all, > > I have some questions about CPU load and performance, but first some > background information. > > We have small embedded system running an openembedded classic (Angström) > distro. Now to get ourselves up-to-date we started working on a new > iteration of the OS based on openembedded core and Yocto. It is nearly > finished now, if it weren't for one problem: The CPU load (/proc/loadavg) of > the core/yocto based OS is more than double that of the classic/Angström OS. > > So the way I see it this could be caused by a number of factors: > > - loadavg's calculation changed > - certain newer versions of applications run heavier > - The kernel itself is heavier (we upgraded from 2.6.35.14+ to 4.9.28+) > - Possibly caused by some configs > - ... > > My question: is there something that changed since OE-classic that you know > could be the cause of this? If not, how would I go about finding the cause? > I don't think the top command is sufficient for this, because it's precision > is such that many processes' CPU usage just become 0%. You don't say what the CPU doubled from or too. 1% to 2%, or 50% to 100% ? Unless the absolute increase is very small, you can probably ignore the processes which top reports as 0%. Does the new build have any significant processes running which weren't there in the old build? Or is it the same basic set of apps running in each? > Also, both top and > htop cause huge cpu loads themselves. > > Any tips and tricks would be welcome! > > Thanks in advance! > > Ryan > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2018-03-29 1:24 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-27 11:44 CPU Load Ryan Meulenkamp 2018-03-29 1:24 ` Andre McCurdy [this message] 2018-03-29 1:24 ` [yocto] " Andre McCurdy 2018-03-29 6:42 ` Jussi Laako -- strict thread matches above, loose matches on Subject: below -- 2007-02-12 16:57 CPU load Andrew Burgess 2007-02-12 18:15 ` malc 2007-02-12 5:33 Vassili Karpov 2007-02-12 5:44 ` Con Kolivas 2007-02-12 5:54 ` malc 2007-02-12 6:12 ` Con Kolivas 2007-02-12 7:10 ` malc 2007-02-12 7:29 ` Con Kolivas 2007-02-12 5:55 ` Stephen Rothwell 2007-02-12 6:08 ` Con Kolivas 2007-02-12 14:32 ` Pavel Machek 2007-02-13 22:01 ` malc 2007-02-13 22:08 ` Con Kolivas 2007-02-14 7:28 ` malc 2007-02-14 8:09 ` Con Kolivas 2007-02-14 20:45 ` Pavel Machek 2007-02-25 10:35 ` malc 2007-02-26 9:28 ` Pavel Machek 2007-02-26 10:42 ` malc 2007-02-26 16:38 ` Randy Dunlap 2007-02-12 18:05 ` malc 2002-07-10 14:50 David Chow 2002-07-10 16:54 ` William Lee Irwin III 2002-07-10 17:49 ` Robert Love 2002-07-26 17:38 ` David Chow
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='CAJ86T=WE6khW6vfL2_z3HdXjB-pxSSaTAb=Fz-NSczhTGxV=HQ@mail.gmail.com' \ --to=armccurdy@gmail.com \ --cc=Ryan.Meulenkamp@nedap.com \ --cc=openembedded-core@lists.openembedded.org \ --cc=yocto@yoctoproject.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.