From: David Collier-Brown <davec-b@rogers.com>
To: "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] go's improvements to gc
Date: Thu, 29 Nov 2018 20:47:17 -0500 [thread overview]
Message-ID: <dcc20428-6c33-b304-f429-3b64eb86d706@rogers.com> (raw)
In-Reply-To: <CAA93jw67HVCmmpuCuCwjQwEsjFp0JEoLt+RupMYqD=n3B4P5sw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
If you can think in terms of pipes, Go makes you /productive/. I
recognized that about 13 hours into learning Go about two years ago.
My advice as an aphorism: "redo something you've done at least once
before, in go, and see how different it it. Then decide if it's better"
--dave
On 2018-11-29 8:33 p.m., Dave Taht wrote:
> as remarkable as our efforts have been to reduce network bloat, I have
> to take my hat off to the
> golang garbage collection folk, also.
>
> Reductions in latencies from 300ms to 500us in 4 years. Good story
> here about how latency is cumulative:
>
> https://blog.golang.org/ismmkeynote
>
> The very first thing I learned about go, was how to turn off the
> garbage collector. I guess I have to go learn some go, for real, now.
>
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
[-- Attachment #2: Type: text/html, Size: 1621 bytes --]
prev parent reply other threads:[~2018-11-30 1:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 1:33 Dave Taht
2018-11-30 1:47 ` David Collier-Brown [this message]
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dcc20428-6c33-b304-f429-3b64eb86d706@rogers.com \
--to=davec-b@rogers.com \
--cc=bloat@lists.bufferbloat.net \
--cc=davecb@spamcop.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