Poor performance on low-end ARMv7 devices

OpenSubmitted by Ludovic Courtès.
Details
5 participants
  • Denis 'GNUtoo' Carikli
  • Danny Milosavljevic
  • Julien Lepiller
  • Ludovic Courtès
  • Mathieu Othacehe
Owner
unassigned
Severity
important
L
L
Ludovic Courtès wrote on 14 Apr 2020 15:59
(address . bug-guix@gnu.org)
87a73exj5v.fsf@inria.fr
Hello!

On my Olimex OLinuXino A20, here’s what I get with Guix on Guile 3.0.2:

Toggle snippet (13 lines)
$ guix describe
Generation 1 Apr 11 2020 13:26:01 (current)
guix 6720616
repository URL: https://git.savannah.gnu.org/git/guix.git
commit: 6720616daaf711314827c157a660339990e5cb07
$ time guix build hello -d --no-grafts
/gnu/store/s0di07vhva95rl8p3gimlna5ffca7xlq-hello-2.10.drv

real 0m9.964s
user 0m8.660s
sys 0m0.810s

Most of it seems to go in loading .go files:

Toggle snippet (17 lines)
$ guix repl
GNU Guile 3.0.2
Copyright (C) 1995-2020 Free Software Foundation, Inc.

Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.

Enter `,help' for help.
scheme@(guix-user)> ,time (use-modules (guix) (gnu) (gnu packages base))
;; 8.104000s real time, 6.879000s run time. 0.755000s spent in GC.
scheme@(guix-user)> (define s (open-connection))
scheme@(guix-user)> ,time (package-derivation s hello #:graft? #f)
$1 = #<derivation /gnu/store/s0di07vhva95rl8p3gimlna5ffca7xlq-hello-2.10.drv => /gnu/store/z4ig2v79x3y7r5w1gs7rg7cgyvja4dn1-hello-2.10 31a5bb8>
;; 3.101000s real time, 2.493000s run time. 0.324000s spent in GC.

Ludo’.
J
J
Julien Lepiller wrote on 14 Apr 2020 20:08
2AB0E1B2-4104-4378-B872-DF8E3673D15B@lepiller.eu
Le 14 avril 2020 09:59:24 GMT-04:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
Toggle quote (43 lines)
>Hello!
>
>On my Olimex OLinuXino A20, here’s what I get with Guix on Guile 3.0.2:
>
>--8<---------------cut here---------------start------------->8---
>$ guix describe
>Generation 1 Apr 11 2020 13:26:01 (current)
> guix 6720616
> repository URL: https://git.savannah.gnu.org/git/guix.git
> commit: 6720616daaf711314827c157a660339990e5cb07
>$ time guix build hello -d --no-grafts
>/gnu/store/s0di07vhva95rl8p3gimlna5ffca7xlq-hello-2.10.drv
>
>real 0m9.964s
>user 0m8.660s
>sys 0m0.810s
>--8<---------------cut here---------------end--------------->8---
>
>Most of it seems to go in loading .go files:
>
>--8<---------------cut here---------------start------------->8---
>$ guix repl
>GNU Guile 3.0.2
>Copyright (C) 1995-2020 Free Software Foundation, Inc.
>
>Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
>This program is free software, and you are welcome to redistribute it
>under certain conditions; type `,show c' for details.
>
>Enter `,help' for help.
>scheme@(guix-user)> ,time (use-modules (guix) (gnu) (gnu packages
>base))
>;; 8.104000s real time, 6.879000s run time. 0.755000s spent in GC.
>scheme@(guix-user)> (define s (open-connection))
>scheme@(guix-user)> ,time (package-derivation s hello #:graft? #f)
>$1 = #<derivation
>/gnu/store/s0di07vhva95rl8p3gimlna5ffca7xlq-hello-2.10.drv =>
>/gnu/store/z4ig2v79x3y7r5w1gs7rg7cgyvja4dn1-hello-2.10 31a5bb8>
>;; 3.101000s real time, 2.493000s run time. 0.324000s spent in GC.
>--8<---------------cut here---------------end--------------->8---
>
>Ludo’.

In case it helps, I observe the same kind of timing on my cubietruck (same guile, but guix from april 1st). It's slightly faster than you, the processor is a cortex-a7.
D
D
Danny Milosavljevic wrote on 14 Apr 2020 21:08
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 40626@debbugs.gnu.org)
20200414210859.4529c305@scratchpost.org
For comparison, on a Banana Pi M2 Ultra I get:

root@bpi-iot-ros-ai:/# time guix build hello -d --no-grafts
/gnu/store/yp46hszc04dx2zy6kscy1zmjfg9y8flq-hello-2.10.drv

real 0m13.481s
user 0m11.230s
sys 0m0.900s

root@bpi-iot-ros-ai:/# time guix build hello -d --no-grafts
/gnu/store/yp46hszc04dx2zy6kscy1zmjfg9y8flq-hello-2.10.drv

real 0m11.471s
user 0m10.820s
sys 0m0.380s

root@bpi-iot-ros-ai:/# guix repl
GNU Guile 2.2.4
Copyright (C) 1995-2017 Free Software Foundation, Inc.

Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.

Enter `,help' for help.
scheme@(guix-user)> ,time (use-modules (guix) (gnu) (gnu packages base))
;; 3.360000s real time, 3.270000s run time. 0.519000s spent in GC.
scheme@(guix-user)> (define s (open-connection))
scheme@(guix-user)> ,time (package-derivation s hello #:graft? #f)
$1 = #<derivation /gnu/store/yp46hszc04dx2zy6kscy1zmjfg9y8flq-hello-2.10.drv => /gnu/store/cp0qvs3vxrqiyyxfi8556n52x7ax8khf-hello-2.10 14fabb8>
;; 6.829000s real time, 6.579000s run time. 1.019000s spent in GC.

Processor is a Cortex A7.

Note:

You can do some RAM training and if RAM is connected better on your board,
you can sometimes have staggering speed gains.

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl6WCksACgkQ5xo1VCww
uqWCRwgAk/gZNM0K1fkKPY0GAcMJd9nmg98vl6uP2o/b68KyQOKkCAtbeZiOh0zd
voN+sVLhPZ/x/V7ByWeKODL6ySL9KYrK7FBzIc4S+5g1yU0uQ4AA2kKfrZDlPQpA
uKvmrN+KEbs69VLvqDPVqVq+zOpL9NwdZGshpkIBWruiOfCFFMSFYPA5UsGEKHrO
lVRKBkvODoEOS+Tnq51yfo0RXxgmg4Iy4Um0C0ynZ4Bsbbs2bDIZK8AnADTNyRos
yW5lra6BWpgADGJSJBfNorzVE9Nrn4ZlZR4QR0KmR0ngv7EloCyvnWbPNEPFfO3Q
sGWlaQXFvx75qGp4HKHwd4Jd/qOROA==
=oHvp
-----END PGP SIGNATURE-----


L
L
Ludovic Courtès wrote on 14 Apr 2020 22:01
(name . Danny Milosavljevic)(address . dannym@scratchpost.org)(address . 40626@debbugs.gnu.org)
87sgh5vnup.fsf@gnu.org
Hi Danny,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

Toggle quote (3 lines)
> root@bpi-iot-ros-ai:/# guix repl
> GNU Guile 2.2.4

This is a fairly old Guix though, so not directly comparable.

Could you try with a current Guix?

(Yeah, you’ll have to pull, and that takes verrrrry loong. Be sure to
pick a commit that’s fully built on

Ludo’.
L
L
Ludovic Courtès wrote on 16 Apr 2020 10:22
control message for bug #40626
(address . control@debbugs.gnu.org)
87tv1jkfg4.fsf@gnu.org
severity 40626 important
quit
L
L
Ludovic Courtès wrote on 16 Apr 2020 17:21
Re: bug#40626: Poor performance on low-end ARMv7 devices
(address . 40626@debbugs.gnu.org)
875zdzihh4.fsf@gnu.org
Ludovic Courtès <ludo@gnu.org> skribis:

Toggle quote (2 lines)
> Most of it seems to go in loading .go files:

On x86_64, I’ve run:

./pre-inst-env perf record guile -c '(use-modules (gnu packages libreoffice))'

which shows mostly GC activity, along with symbol interning activity:

Toggle snippet (21 lines)
14.71% guile libgc.so.1.3.6 [.] GC_mark_from
7.49% guile libgc.so.1.3.6 [.] GC_header_cache_miss
5.56% guile libguile-3.0.so.1.1.1 [.] vm_regular_engine
5.42% guile libgc.so.1.3.6 [.] GC_add_to_black_list_normal
2.66% guile libpthread-2.29.so [.] __pthread_mutex_unlock_usercnt
2.63% guile libgc.so.1.3.6 [.] GC_find_header
2.09% guile ld-2.29.so [.] _dl_update_slotinfo
1.88% guile libguile-3.0.so.1.1.1 [.] scm_c_weak_set_lookup
1.68% guile libguile-3.0.so.1.1.1 [.] narrow_string_hash
1.64% guile libguile-3.0.so.1.1.1 [.] scm_i_is_narrow_string
1.55% guile libguile-3.0.so.1.1.1 [.] scm_ihashq
1.52% guile libguile-3.0.so.1.1.1 [.] scm_sloppy_assq
1.32% guile libgc.so.1.3.6 [.] GC_move_disappearing_link_inner
1.23% guile libgc.so.1.3.6 [.] GC_malloc_kind
1.23% guile libpthread-2.29.so [.] __pthread_mutex_lock
1.22% guile libguile-3.0.so.1.1.1 [.] scm_hash_fn_get_handle
1.19% guile libpthread-2.29.so [.] __pthread_mutex_trylock
1.12% guile libguile-3.0.so.1.1.1 [.] get_callee_vcode
1.12% guile libguile-3.0.so.1.1.1 [.] scm_equal_p

Back on my A20 board, I get this (unhelpful) GC profile:

Toggle snippet (27 lines)
scheme@(guix-user)> ,use(statprof)
scheme@(guix-user)> (gcprof (lambda () (resolve-module '(gnu packages base))))
% cumulative self
time seconds seconds procedure
100.00 5.13 5.13 ice-9/boot-9.scm:2201:0:%load-announce
0.00 4081.53 0.00 ice-9/boot-9.scm:220:5:map1
0.00 621.21 0.00 ice-9/threads.scm:388:4
0.00 310.61 0.00 ice-9/boot-9.scm:2803:0:save-module-excursion
0.00 310.61 0.00 anon #x1b15600
0.00 310.61 0.00 ice-9/boot-9.scm:3211:7
0.00 310.61 0.00 ice-9/boot-9.scm:3500:5
0.00 310.61 0.00 ice-9/boot-9.scm:3508:21
0.00 305.47 0.00 ice-9/boot-9.scm:3256:0:resolve-interface
0.00 295.21 0.00 ice-9/boot-9.scm:3381:5
0.00 295.21 0.00 ice-9/boot-9.scm:3351:0:define-module*
0.00 5.13 0.00 anon #xb2d8d098
0.00 5.13 0.00 anon #xb32d0098
0.00 5.13 0.00 anon #xb2fca098
0.00 5.13 0.00 anon #xb32e2098
0.00 5.13 0.00 anon #xb3343098
0.00 5.13 0.00 ice-9/boot-9.scm:2557:0:call-with-deferred-observers
[…]
---
Sample count: 2
Total time: 5.134 seconds (0.44 seconds in GC)

and this profile:

Toggle snippet (34 lines)
scheme@(guix-user)> ,pr (resolve-module '(gnu packages base))
% cumulative self
time seconds seconds procedure
17.86 1.38 1.38 ice-9/boot-9.scm:2201:0:%load-announce
5.36 0.41 0.41 ice-9/boot-9.scm:3545:0:autoload-done!
4.76 0.37 0.37 ice-9/boot-9.scm:3540:0:autoload-done-or-in-progress?
4.76 0.37 0.37 anon #x1a671cc
4.17 0.32 0.32 ice-9/format.scm:113:2:format:format-work
3.57 0.28 0.28 ice-9/boot-9.scm:3552:0:autoload-in-progress!
2.98 0.55 0.23 ice-9/boot-9.scm:1396:0:symbol-append
2.98 0.23 0.23 anon #x1a65c28
1.79 0.32 0.14 ice-9/boot-9.scm:2729:0:module-make-local-var!
1.79 0.14 0.14 anon #x1a671a4
1.79 0.14 0.14 anon #x1a6c284
1.79 0.14 0.14 anon #x1a67644
1.79 0.14 0.14 ice-9/boot-9.scm:3209:4
1.19 6106.96 0.09 ice-9/boot-9.scm:220:5:map1
1.19 518.54 0.09 ice-9/boot-9.scm:3211:7
1.19 511.19 0.09 ice-9/boot-9.scm:3381:5
1.19 5.69 0.09 anon #xb13f9098
1.19 0.18 0.09 anon #xad994098
1.19 0.09 0.09 anon #x1a6848c
1.19 0.09 0.09 srfi/srfi-60.scm:57:0:bitwise-if
1.19 0.09 0.09 ice-9/boot-9.scm:2468:2
1.19 0.09 0.09 ice-9/boot-9.scm:2468:2
1.19 0.09 0.09 anon #x1a6e284
1.19 0.09 0.09 anon #x1a67cd4
1.19 0.09 0.09 anon #x1a6e87c
[…]
---
Sample count: 168
Total time: 7.714 seconds (1.279 seconds in GC)

What’s the deal with ‘%load-announce’? How many times is it called?

Toggle snippet (54 lines)
$ guix repl
GNU Guile 3.0.2
Copyright (C) 1995-2020 Free Software Foundation, Inc.

Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.

Enter `,help' for help.
scheme@(guix-user)> ,use(system vm vm)
scheme@(guix-user)> (set-vm-engine! 'debug)
scheme@(guix-user)> ,use(statprof)
scheme@(guix-user)> (statprof (lambda () (resolve-module '(gnu packages base))) #:count-calls? #t)
% cumulative self
time seconds seconds calls procedure
5.31 4.39 4.39 anon #x1ba81cc
3.84 98371.57 3.17 69196 ice-9/boot-9.scm:220:5:map1
3.32 2.75 2.75 57783 ice-9/boot-9.scm:2468:2
3.26 2.70 2.70 anon #x1ba81a4
3.01 2.49 2.49 60626 ice-9/boot-9.scm:1299:5
2.94 9.23 2.43 44668 ice-9/boot-9.scm:2757:0:module-add!
2.85 4.39 2.35 47021 ice-9/boot-9.scm:2549:0:module-modified
2.53 2.09 2.09 44668 ice-9/boot-9.scm:2652:0:module-obarray-set!
2.33 1.93 1.93 anon #x1ba6c28
2.24 1.85 1.85 anon #x1baa1fc
2.21 1.83 1.83 anon #x1bad284
2.11 1.75 1.75 anon #x1ba8cd4
2.01 4.55 1.67 32603 ice-9/boot-9.scm:2790:0:module-ref-submodule
1.92 1.59 1.59 anon #x1ba8f34
1.89 1.56 1.56 21349 ice-9/boot-9.scm:806:0:and=>
1.76 1.46 1.46 32184 ice-9/boot-9.scm:2468:2
1.69 1.40 1.40 33343 ice-9/boot-9.scm:2468:2
1.69 1.40 1.40 anon #x1ba8080
1.50 15.24 1.24 19850 ice-9/boot-9.scm:3339:29
1.44 7457.26 1.19 7325 ice-9/boot-9.scm:3256:0:resolve-interface
1.44 1.19 1.19 19133 ice-9/boot-9.scm:3345:2
1.41 9.79 1.16 19217 ice-9/boot-9.scm:1396:0:symbol-append
1.37 1.14 1.14 20160 ice-9/boot-9.scm:2468:2
1.34 1.11 1.11 19850 ice-9/boot-9.scm:3303:48
1.34 1.11 1.11 14322 srfi/srfi-60.scm:57:0:bitwise-if
1.31 1.08 1.08 36200 anon #x1ba6c18
1.15 2.65 0.95 9672 ice-9/vlist.scm:544:0:vhash-assv
1.15 2.09 0.95 20671 ice-9/boot-9.scm:215:2:map
1.15 0.95 0.95 14210 ice-9/boot-9.scm:3209:4
1.12 7.09 0.93 12743 ice-9/boot-9.scm:2729:0:module-make-local-var!
1.05 0.87 0.87 11594 guix/utils.scm:810:0:source-properties->location
0.99 1.35 0.82 11559 ice-9/boot-9.scm:2746:0:module-ensure-local-variable!
0.90 0.74 0.74 370 ice-9/boot-9.scm:2201:0:%load-announce
[…]
---
Sample count: 3128
Total time: 82.752 seconds (16.401 seconds in GC)

Only 370 times.

Hmm could something be wrong with the mapping of instruction pointers to
source code location?

Ludo’.
D
D
Denis 'GNUtoo' Carikli wrote on 3 Jul 2020 01:57
Re: Poor performance on low-end ARMv7 devices
(address . 40626@debbugs.gnu.org)
20200703015725.11a6515c@primarylaptop.localdomain
Hi,

Many ARM Single Board Computers are commonly used with microSD for
storage, and some microSD cards are extremely slow (and sometimes
unreliable when they are old).

Could the performance issues be related to storage device I/Os?

Denis.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEeC+d2+Nrp/PU3kkGX138wUF34mMFAl7+dGUACgkQX138wUF3
4mN9Ag//dM8BxgVhrFiAr4LDqWdAaRwyu0XfWTzfGZNIfFSXQKHk5wzRwlvVmQTs
zi0xEs8bP7tMJ3Op2ZxrM8lOJvYXSzBclnC8Vh8xKHcD+99IzE79bNKX0UYOSNLM
X4gI6jfIJZyVe13IGUSWhCxbZTfR0/cHgegonsJ+Ajr8FH2Qvv6kvgsAqio74ujK
+iQwjTWCT4+K3VGfyGhjTcfRmoSV6DfqhOP12mMevf6YYwv6iu2a7f9vE1FxibrV
ckwYQsXryfmHMzOUMuqbqolwOQu8xdGURHFn14RcYibeYemrryWQpkNaN1SPk5T7
svL3kQ1uGH774arVGc8ULozDr8TpdkTD8iCTF457Zm5F42MT5tYuKqGSselvtE3K
50Lw6yYSravSl2XjUWwUs+MxCKD0OYb2/S9e2QoY1M/vQeefX/YVX3s1ZsHMsUZk
LDE40I9NVk6MnCSWILlMq257r/n7OP/vt6tGnmxRpAnCczAz5Iyv1nWU2OuuFwSO
5T81LGcZuT0RTPk4GyttybmQdXihNpk/1yRfacnFZ+QNzsK2AaSBgLiO2ZJOPACL
XddcqUW+vZJF2kuYoQ6Hv+bND3hMrtWToKUzjSYKgC4iurBtTqlM0v0kz6hd8M28
2Lj4kAEefihgQUt7S3f77sjNptQxlviUyEX4/2PUh3nlDAsB4Vc=
=Zxkt
-----END PGP SIGNATURE-----


M
M
Mathieu Othacehe wrote on 3 Jul 2020 09:22
Re: bug#40626: Poor performance on low-end ARMv7 devices
(name . Denis 'GNUtoo' Carikli)(address . GNUtoo@cyberdimension.org)(address . 40626@debbugs.gnu.org)
873669kqpj.fsf@gnu.org
Hello,

Toggle quote (6 lines)
> Many ARM Single Board Computers are commonly used with microSD for
> storage, and some microSD cards are extremely slow (and sometimes
> unreliable when they are old).
>
> Could the performance issues be related to storage device I/Os?

For those ARMv7 devices, which have few substitutes available and not
much computation power, an approach is to work from a x86 machine and
cross-compile disk-images.

We will also have network booting supported soon, which will allow to do
the same, but without having to write an SD card.

In the meantime I would propose to close this bug, as there's not much
that can be done, I think.

Thanks,

Mathieu
L
L
Ludovic Courtès wrote on 13 Jul 2020 15:34
(name . Denis 'GNUtoo' Carikli)(address . GNUtoo@cyberdimension.org)(address . 40626@debbugs.gnu.org)
87ft9vr12g.fsf@gnu.org
Hi,

Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> skribis:

Toggle quote (6 lines)
> Many ARM Single Board Computers are commonly used with microSD for
> storage, and some microSD cards are extremely slow (and sometimes
> unreliable when they are old).
>
> Could the performance issues be related to storage device I/Os?

It could be the reason; it’s definitely the case on the board I was
using here.

Still I wonder what could be done on our side to improve on this.

Ludo’.
D
D
Denis 'GNUtoo' Carikli wrote on 14 Jul 2020 06:39
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 40626@debbugs.gnu.org)
20200714063959.19196a53@primarylaptop.localdomain
On Mon, 13 Jul 2020 15:34:15 +0200
Ludovic Courtès <ludo@gnu.org> wrote:

Toggle quote (14 lines)
> Hi,
>
> Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> skribis:
>
> > Many ARM Single Board Computers are commonly used with microSD for
> > storage, and some microSD cards are extremely slow (and sometimes
> > unreliable when they are old).
> >
> > Could the performance issues be related to storage device I/Os?
>
> It could be the reason; it’s definitely the case on the board I was
> using here.
>
> Still I wonder what could be done on our side to improve on this.
I guessed that was the intent.

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.

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.

Denis.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEeC+d2+Nrp/PU3kkGX138wUF34mMFAl8NNyAACgkQX138wUF3
4mPm7hAAlyGuNNBHykJhMYi8Zs4PUV4lNWRrvMfc0aO4JufCTJJgqfMooZppiFoe
U5bbMB5I4bkdp5DfxUdkTQU+mq2zy4QoX3OhjyBUrgQJUfIkIsdMNOih96rjnI+J
St3tLK7rnTLzNCOYCOUpXCFQD9lESkTZwgkF/nsuoCU3L1YbQpub/JZHANef9FFA
iR9/UzpVIvLCr06U8vDKVt/RV8Xw5ZBlxHtAQhWENOc/o4ljTGCLbhsGhx0Ee9Az
c27U0YUUcg/8X67n1u2Wr/idSmOHzqgnUuO9fRQlwRAI02o4lqe10ALrScWmD0U5
lBPUMCseL//HQWCM+raUeh/Ya/fRiBhm6WkxNv8xeACS5w+82zPR9PUc5OzJ8LOz
0hogEPmvqRpyfqHB+et5CiL+Y16gyof42wnNVIeGsbXrMMUTuPofBqI4ric6EUKL
Uj/H+PrthFJF+v2qpuOGHFv0Sb2OkFMdJfNj0ZfTVdM4olmGRXPBzV+F9f+cxVOC
ReTmE1WbfNXOpekrSQ+ez/v9JJfVBvd3G6CGmRbJJMRn9qHfsgQndzN/hb8wyE/t
4K+32vItRvqC7/I/pRzP4GrVtOhRJCczoFNG04eyCVpW4VtymLPTPpxjmbY5Rmse
CV/9ClF1JdhPdCJODtx1/O7797uZxFDMi4pVjU+HpUncKbYbTD0=
=vYYm
-----END PGP SIGNATURE-----


L
L
Ludovic Courtès wrote on 14 Jul 2020 15:05
(name . Denis 'GNUtoo' Carikli)(address . GNUtoo@cyberdimension.org)(address . 40626@debbugs.gnu.org)
87ft9umel6.fsf@gnu.org
Hi,

Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> skribis:

Toggle quote (9 lines)
> 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.

Toggle quote (14 lines)
> 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’.
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send email to 40626@debbugs.gnu.org