From: "David P. Reed" <dpreed@deepplum.com>
To: "Jonathan Morton" <chromatix99@gmail.com>
Cc: "Joel Wirāmu Pauling" <joel@aenertia.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] openwrt or "open" security cams?
Date: Sat, 4 Apr 2020 09:37:05 -0400 (EDT) [thread overview]
Message-ID: <1586007425.489720655@apps.rackspace.com> (raw)
In-Reply-To: <A32D17D2-FB03-44EB-8CED-D4C05E68D20D@gmail.com>
I have some servers with 512 GB of RAM, and my company sells "Software Defined Server" capability to relatively inexpensively make virtualized systems with 10 TB of RAM out of these 512 GB systems. They fit in less then a single 19" rack.
[Couldn't resist :-) https://www.tidalscale.com/technology is the place to learn more.
More OT: We deal with "bloat" at a different scale in our Ethernet internal to our software defined server implementation, since our interconnects are 10 GigE up to 100 GigE, but I can tell you it is a problem there, too. Serious problem if you by Arista gear, which is bloated by intent :-( because latency doesn't occur to Bechtolsheim to be a problem, only throughput. Fortunately, we (my design) control the network stack in the hyperkernel, and can use speciaized end-to-end protocols that don't use the bloat.
Anyway, my actual non-work desktop has 32 GB RAM. So 128 GB isn't surprising in my context.]
On Friday, April 3, 2020 7:10pm, "Jonathan Morton" <chromatix99@gmail.com> said:
>> On 4 Apr, 2020, at 2:08 am, Joel Wirāmu Pauling <joel@aenertia.net> wrote:
>>
>> 128G of Ram
>
> That's somewhat more than I have in my desktop PCs. Did you mean 128MB?
>
> - Jonathan Morton
>
>
next prev parent reply other threads:[~2020-04-04 13:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 18:05 Dave Taht
2020-04-03 22:53 ` David P. Reed
2020-04-03 23:08 ` Joel Wirāmu Pauling
2020-04-03 23:10 ` Jonathan Morton
2020-04-03 23:15 ` Joel Wirāmu Pauling
2020-04-04 13:37 ` David P. Reed [this message]
2020-04-03 23:32 ` Valdis Klētnieks
2020-04-03 23:36 ` Joel Wirāmu Pauling
2020-04-04 0:28 ` Dave Taht
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1586007425.489720655@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=joel@aenertia.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