mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-omap@vger.kernel.org, sre@kernel.org, nekit1000@gmail.com,
	mpartap@gmx.net, merlijn@wizzup.org
Subject: Re: v4.18-rc1 on droid 4: very bad CPU performance
Date: Fri, 22 Jun 2018 00:49:36 -0700	[thread overview]
Message-ID: <20180622074936.GG112168@atomide.com> (raw)
In-Reply-To: <20180622072005.GF112168@atomide.com>

* Tony Lindgren <tony@atomide.com> [180622 07:22]:
> * Pavel Machek <pavel@ucw.cz> [180621 12:18]:
> > Hi!
> > 
> > V4.18 is slower than it should be.
> > 
> > user@devuan:~$ time cat /dev/urandom | head -c 10000000 |  bzip2 -9 -
> > | wc -c
> > 10044291
> > 52.73user 2.40system 61.53 (1m1.534s) elapsed 89.60%CPU
> > user@devuan:~$ uname -a
> > Linux devuan 4.18.0-rc1-87964-gfa19934-dirty #743 SMP Sun Jun 17
> > 19:26:37 CEST 2018 armv7l GNU/Linux
> > 
> > That bzip should take 12 seconds, not minute.
> > 
> > Any ideas? Do you see it, too?
> 
> I've noticed firefox is super slow.. Git bisect time?

Hmm not happening for me at least on duovero and droid4,
I'm getting about 20s for v4.17 and v4.18-rc1.

Regards,

Tony

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-21 12:15 Pavel Machek
2018-06-22  7:20 ` Tony Lindgren
2018-06-22  7:49   ` Tony Lindgren [this message]
2018-06-25  9:49     ` Pavel Machek
2018-06-26  6:16       ` Tony Lindgren
2018-06-27 13:26         ` Pavel Machek
2018-06-27 19:48         ` Pavel Machek
2018-06-27 20:58     ` Pavel Machek
2018-06-28  9:06       ` Tony Lindgren
2018-07-04 20:12         ` Pavel Machek
2018-07-04 20:22         ` Pavel Machek

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=20180622074936.GG112168@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=merlijn@wizzup.org \
    --cc=mpartap@gmx.net \
    --cc=nekit1000@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=sre@kernel.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

Powered by JetHome