Date: Fri, 5 Oct 2018 11:30:38 -0700 From: Mark Millard <marklmi@yahoo.com> To: freebsd-arm <freebsd-arm@freebsd.org> Subject: FYI: SoftIron Overdrive 1000 vs. Pine64+ 2GB buildworld buildkernel time examples (fairly modern head versions) Message-ID: <37BC2D1A-594A-425F-B4EB-1B1118B4B5B2@yahoo.com>
next in thread | raw e-mail | index | archive | help
Self hosted (re-)build from scratch (empty build tree at start): SoftIron Overdrive 1000: a little under 3 hrs and 20 min Pine64+ 2GB: a little under 13 hrs and 45 min So somewhat more than a 10 hour difference and a factor of somewhat over 4 for total time. (I was testing the Overdrive and was curious. The Overdrive 1000 seems to be working fine.) Supporting context details (including the unusual storage) if you care . . . Both had: make[1]: "/usr/src/Makefile.inc1" line 341: SYSTEM_COMPILER: Determined = that CC=3Dcc matches the source tree. Not bootstrapping a = cross-compiler. make[1]: "/usr/src/Makefile.inc1" line 346: SYSTEM_LINKER: Determined = that LD=3Dld matches the source tree. Not bootstrapping a cross-linker. and: #WITH_CROSS_COMPILER=3D WITH_SYSTEM_COMPILER=3D WITH_SYSTEM_LINKER=3D # #CPUTYPE=3Dsoft WITH_LIBCPLUSPLUS=3D #WITH_LLD_BOOTSTRAP=3D WITHOUT_BINUTILS_BOOTSTRAP=3D WITH_ELFTOOLCHAIN_BOOTSTRAP=3D WITH_LLVM_TARGET_ALL=3D #WITH_CLANG_BOOTSTRAP=3D WITH_CLANG=3D WITH_CLANG_IS_CC=3D WITH_CLANG_FULL=3D WITH_CLANG_EXTRAS=3D WITH_LLD=3D WITH_LLD_IS_LD=3D WITHOUT_BINUTILS=3D WITH_LLDB=3D # WITH_BOOT=3D WITHOUT_LIB32=3D # WITHOUT_GCC_BOOTSTRAP=3D WITHOUT_GCC=3D WITHOUT_GCC_IS_CC=3D WITHOUT_GNUCXX=3D # NO_WERROR=3D #WERROR=3D MALLOC_PRODUCTION=3D Both were using: LDFLAGS.lld+=3D -Wl,--no-threads (via make.conf). Both were running non-debug builds (with symbols), including for the kernel. Both were building non-debug builds (with symbols). The file system is UFS with soft updates (no journaling) in both cases. File systems each is one partition. Trim enabled, vfs.ffs.dotrimcons=3D1 . fsck_ffs -E had been used in a prior boot in both cases. vm.pageout_oom_seq=3D120 was in use for both. (The default of 12 is not sufficient for the Pine64+ 2GB to complete buildworld buildkernel.) The Overdrive context was based on: CFLAGS.clang+=3D -mcpu=3Dcortex-a57 CXXFLAGS.clang+=3D -mcpu=3Dcortex-a57 CPPFLAGS.clang+=3D -mcpu=3Dcortex-a57 ACFLAGS.arm64cpuid.S+=3D -mcpu=3Dcortex-a57+crypto ACFLAGS.aesv8-armx.S+=3D -mcpu=3Dcortex-a57+crypto ACFLAGS.ghashv8-armx.S+=3D -mcpu=3Dcortex-a57+crypto and was a -r339076 context building itself. The Pine64+ 2GB context was based on: CFLAGS.clang+=3D -mcpu=3Dcortex-a53 CXXFLAGS.clang+=3D -mcpu=3Dcortex-a53 CPPFLAGS.clang+=3D -mcpu=3Dcortex-a53 ACFLAGS.arm64cpuid.S+=3D -mcpu=3Dcortex-a53+crypto ACFLAGS.aesv8-armx.S+=3D -mcpu=3Dcortex-a53+crypto ACFLAGS.ghashv8-armx.S+=3D -mcpu=3Dcortex-a53+crypto and was a -r338860 context building itself. (Some notes are from memory for this older build.) The Overdrive had the hard disk replaced by a SanDisk 860 Pro SSD (1TB). Around 95% of the space being free. It still had the original 8 GiByte RAM. 28 GiByte swap space on the same media. My modified version of top reported for the Overdrive: no observed use of swap. My modified version of top reported: Maximum Observed Active Mem 1627M. No observed use of Swap. The Pine64+ 2GB had a 128 GB e.MMC on a microsd adapter (used in DDR52 mode via local changes). Around 50% of the space being free. 3584M swap space on the same media. My modified version of top reported: Maximum Observed Active Mem 1501M. Maximum Observed Used Swap 198M. The Pine64+ 2GB does have a case, heat sinks, and a fan, but by no means equivalent to the Overdrive configuration. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37BC2D1A-594A-425F-B4EB-1B1118B4B5B2>