Self-Contained Pure-Go Web Server with Lua, MD, HTTP/2, QUIC, Redis Support

Re:Self-Contained Pure-Go Web Server with Lua, MD, HTTP/2, Q... by chx on Thursday April 04, 2019 @11:03PM (#19579302)

You would need find an application where the binary image size is a problem. In an age where 1TB SSDs are 300 USD this will be ... challenging. You are able to have about a thousand gigabyte sized images on that one SSD and I suspect you will hit CPU and I/O limits well before you have a thousand different binaries running for real.

Media storage would go on spinning rust disks anyways separate from the SSD(s).

[ Parent | on HN ]

Re:Self-Contained Pure-Go Web Server with Lua, MD, HTTP/2, Q... by derefr on Friday April 05, 2019 @02:13AM (#19580135)

The consideration isn’t binary size, but hot-loop cache coherency. Big binaries cause code-segment cache-line eviction.

[ Parent | on HN ]

Re:Self-Contained Pure-Go Web Server with Lua, MD, HTTP/2, Q... by nolok on Friday April 05, 2019 @06:22AM (#19581202)

Then that's a typical case of optimizing on the wrong metric.

Find a case where it's actually too slow, ok, but saying "A does X, and X can lead to Y, therefore A does Y" is wrong.

If you say the size of the binary is an issue, then give the issue, not how it could (or not) be an issue.

[ Parent | on HN ]

Re:Self-Contained Pure-Go Web Server with Lua, MD, HTTP/2, Q... by takeda on Thursday April 04, 2019 @11:38PM (#19579478)

We observed noticeable difference in deployment time and auto scaling based on container size.

[ Parent | on HN ]