From: "Ludovic Courtès" <ludo@gnu.org>
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Cc: 40626@debbugs.gnu.org
Subject: bug#40626: Poor performance on low-end ARMv7 devices
Date: Tue, 14 Jul 2020 15:05:41 +0200 [thread overview]
Message-ID: <87ft9umel6.fsf@gnu.org> (raw)
In-Reply-To: <20200714063959.19196a53@primarylaptop.localdomain> (Denis Carikli's message of "Tue, 14 Jul 2020 06:39:59 +0200")
Hi,
Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> skribis:
> A way to deal with that could be to validate if it's actually the case,
> for instance by installing an SSD, and doing performance comparison
> with the time command.
>
> Then if it helps a lot, we probably need to trace the filesystem access
> and optimize it somehow. Maybe that can be done with BPF or gprof, but
> I never looked into obtimizing I/O performances, so I'm unsure if
> that's the right approach. Guile may have profiling tools too.
Yeah, the profiles at <https://issues.guix.gnu.org/40626#5> suggest a
couple of things to investigate in Guile.
> As for benchmarking the CPU, I've patched phoronix-test-suite in a very
> quick and dirty way in Parabola, so we could at least have some
> benchmarks. For now we only have "compilation" benchmarks with source
> code that should be FSDG compliant.
>
> With it I've found that the compilation performances can vary a lot
> between different ARM and x86 boards:
> - An I.MX6 Quad with 2G of RAM is about 4.5x faster than the AM335x of a
> Beaglebone Green with 512M of RAM.
> - A Lime2 A20 is about 1.7x faster than the Beaglebone Green and 2.5x
> slower than the board with the I.MX6 Quad.
> - My smartphone (Galaxy SIII GT-I9300) is about 2x faster than my server
> (PC Engines APU1) for compilation.
Interesting, thanks!
Ludo’.
prev parent reply other threads:[~2020-07-14 13:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 13:59 bug#40626: Poor performance on low-end ARMv7 devices Ludovic Courtès
2020-04-14 18:08 ` Julien Lepiller
2020-04-14 19:08 ` Danny Milosavljevic
2020-04-14 20:01 ` Ludovic Courtès
2020-04-16 15:21 ` Ludovic Courtès
2020-07-02 23:57 ` Denis 'GNUtoo' Carikli
2020-07-03 7:22 ` Mathieu Othacehe
2020-07-13 13:34 ` Ludovic Courtès
2020-07-14 4:39 ` Denis 'GNUtoo' Carikli
2020-07-14 13:05 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ft9umel6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=40626@debbugs.gnu.org \
--cc=GNUtoo@cyberdimension.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).