From: Pete Heist <peteheist@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Flent test hardware
Date: Sun, 5 Nov 2017 19:42:58 +0100 [thread overview]
Message-ID: <1442452F-518E-4DB2-852B-2ACA9CEBB869@gmail.com> (raw)
In-Reply-To: <CAJq5cE15PA_CNSLc73ciKPuS0LFz0dX+LvvK-E6ZQLvn3rB5uw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
> On Nov 5, 2017, at 7:08 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
> I see you've specced them to have PicoPSUs and so on. That isn't exactly the cheapest option, though it is very compact - which I know from experience since my E-450 uses the same. Considering less compact options may improve the price comparison.
>
It's true, but also if I wanted to compare my builds to the ProLiant fairly, they’d have to include 8GB of RAM. So I put up four more builds, two with the cheapest case and PSU I could find on the same site, and two with the same cheap case/PSU but also 8GB of RAM.
The prices are all close enough for me to where I’d just want to choose what’s best. The single-threaded performance of the quad-core CPUs are naturally lower, which may affect something, somehow. It would be nice to be able to try Flent tests on both without buying both, but that’s how it is.
Also, with any build it takes a little more time and there’s the possibility of a compatibility problem vs buying something pre-tested (lessons learned), but these builds do look pretty safe.
[-- Attachment #2: Type: text/html, Size: 1603 bytes --]
next prev parent reply other threads:[~2017-11-05 18:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 13:33 Pete Heist
2017-11-04 15:06 ` Sebastian Moeller
2017-11-04 16:33 ` Pete Heist
2017-11-04 17:25 ` Sebastian Moeller
2017-11-04 18:45 ` Pete Heist
2017-11-05 1:42 ` Bob McMahon
2017-11-05 12:13 ` Jonathan Morton
2017-11-05 14:23 ` Pete Heist
[not found] ` <CAJq5cE0nkn+iDP9NuU2aoSk_G+2cxkZYShj9PfK5u=Fr7fTrLA@mail.gmail.com>
[not found] ` <CAJq5cE13M=fmyh2oQ5UxFCOcoPhZ2nOPEkqRWcT-UdGT60=ezA@mail.gmail.com>
[not found] ` <CAJq5cE1KQ+K9x7k+bnuFvqyNhjsg6mSn_CU4b0h8S1bwo5SXOg@mail.gmail.com>
[not found] ` <CAJq5cE2Tk_TAHES+7O28MjryG-nYHRNJ5OB9WjsCXGSfEgORog@mail.gmail.com>
[not found] ` <CAJq5cE0xkhbXYZ4c1+-9FmKOv1_DFFMJh8hqa-W8jEx+K_xTFg@mail.gmail.com>
2017-11-05 16:24 ` Jonathan Morton
2017-11-05 17:39 ` Pete Heist
2017-11-05 18:08 ` Jonathan Morton
2017-11-05 18:42 ` Pete Heist [this message]
2017-11-05 20:15 ` Jonathan Morton
2017-11-07 0:32 ` Pete Heist
2017-11-05 13:57 ` Pete Heist
2017-11-05 19:42 ` Bob McMahon
2017-11-05 21:41 ` Pete Heist
2017-11-06 20:15 ` Isaac Konikoff
2017-11-06 21:29 ` Bob McMahon
2017-11-07 0:39 ` Dave Taht
2017-11-07 1:37 ` Pete Heist
2017-11-07 10:21 ` Pete Heist
2017-11-08 4:46 ` Bob McMahon
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://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1442452F-518E-4DB2-852B-2ACA9CEBB869@gmail.com \
--to=peteheist@gmail.com \
--cc=chromatix99@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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