unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Steve McIntyre <steve@einval.com>
To: Leo Famulari <leo@famulari.name>
Cc: Vagrant Cascadian <vagrant@debian.org>, guix-devel@gnu.org
Subject: Re: What ARM hardware should we buy and where should we host it?
Date: Wed, 5 Sep 2018 01:05:10 +0100	[thread overview]
Message-ID: <20180905000510.q4pbo3ptidjb3p27@tack.einval.com> (raw)
In-Reply-To: <20180904180318.GB9769@jasmine.lan>

On Tue, Sep 04, 2018 at 02:03:18PM -0400, Leo Famulari wrote:
>On Mon, Sep 03, 2018 at 10:59:38AM -0700, Vagrant Cascadian wrote:
>> One of the most promising seems to be the SynQuacer:
>> 
>>   https://www.96boards.org/product/developerbox/
>> 
>> With a 24-core processor, SATA, PCIe, USB 3.0, micro-atx form-factor,
>> and 4 ram slots (up to 64GB, in theory, but may be picky about
>> ram).
>
>It has 24 cores of Cortex-A53 CPUs, which are intended for "mobile"
>applications (smartphones and similar). IMO, it would be great to get
>more powerful processors. But, if this thing is working for Debian and
>can handle sustained load on all 24 cores, that's already better than
>some of the armhf boards we have. According to that Debian mailing list
>post, this can do both 32 and 64-bit.

Correct.

>Steve, do you find the SynQuacer can handle being fully loaded for
>extended periods of time?

I've been doing rebuilds of the entire Debian archive for the last few
weeks on a Synquacer and some other machines. It's not shown any
issues at all during that period. A53 cores are not all that fast for
single-threaded code, but the CPU is claimed to only hit 5W flat out
on all 24 cores. It's got a large passive heat sink and a small fan in
the PSU. No issues seen.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
  Getting a SCSI chain working is perfectly simple if you remember that there
  must be exactly three terminations: one on one end of the cable, one on the
  far end, and the goat, terminated over the SCSI chain with a silver-handled
  knife whilst burning *black* candles. --- Anthony DeBoer

  reply	other threads:[~2018-09-05  0:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-03 11:37 What ARM hardware should we buy and where should we host it? Ricardo Wurmus
2018-09-03 16:28 ` Tobias Geerinckx-Rice
2018-09-14 21:26   ` Ricardo Wurmus
2018-09-14 22:02     ` Tobias Geerinckx-Rice
2018-09-03 17:59 ` Vagrant Cascadian
2018-09-03 18:11   ` Steve McIntyre
2018-09-04 18:03   ` Leo Famulari
2018-09-05  0:05     ` Steve McIntyre [this message]
2018-09-11 21:33 ` Andreas Enge
2018-09-14 21:37   ` Ricardo Wurmus
2018-09-15 13:42     ` Andreas Enge
2018-09-14 20:22 ` Vagrant Cascadian
2018-09-14 21:28   ` Ricardo Wurmus

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=20180905000510.q4pbo3ptidjb3p27@tack.einval.com \
    --to=steve@einval.com \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=vagrant@debian.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).