Live data from Hacker News

Serving a high-performance blog solely from memory, using Rust

xeiaso.net

61–70 of 143 posts

Re: Serving a high-performance blog solely from memory, using Rust

#61

The tech is cool, but some of the language is so cringy. For example, the statement "websites are social constructs" makes zero sense. You could say that websites are material objects of a symbolic network of computer languages, like physical paper money is a material, fetishized object of the social construct of money. Websites themselves are not constructed socially. Maybe the author means how websites are perceive…

You can downvote all you want; this is the truth

Re: Serving a high-performance blog solely from memory, using Rust

#62

After going to the end of a long post, I'm disappointed to not find any latency or throughput efficiency metrics. Author seems to claim he has a very popular high-traffic blog and it is super fast, faster than all the popular web servers serving static pages. Where's the performance data to prove this? edit: web.dev measure gave this blog post url a performance score of 30/100 which is quite poor.

web.dev seems to give it a poor score primarily because of the YouTube embed … so perhaps Google should heed its own advice?

Re: Serving a high-performance blog solely from memory, using Rust

#63
post #50
post #49

Earlier quoted context omitted.

I'm trying to parse what you are saying here. You removed the CDN and the site got slower? How do you know your site was the one that was fast or just the CDN? IE, the CDN should have added a lot of extra hops and made things slower. To me, this implies the rust code is very poor at opening and closing connections, so the CDNs keep alive is pasting over that issue.

The main thing the CDN provided was nodes on basically every continent that kept the site in cache. Without those servers on every continent keeping the site in cache, it takes longer to get to the netherlands to get the site loaded. The speed of light is only so fast.

> The speed of light is only so fast.

Is the Internet not connected internationally (US -> Europe for example) via cables underneath the ocean? Speed of light would be satellite, light? Not electric current?

Or is electricity flowing through a wire also "speed of light"?

Re: Serving a high-performance blog solely from memory, using Rust

#64
post #50

Earlier quoted context omitted.

The main thing the CDN provided was nodes on basically every continent that kept the site in cache. Without those servers on every continent keeping the site in cache, it takes longer to get to the netherlands to get the site loaded. The speed of light is only so fast.

> The speed of light is only so fast. Is the Internet not connected internationally (US -> Europe for example) via cables underneath the ocean? Speed of light would be satellite, light? Not electric current? Or is electricity flowing through a wire also "speed of light"?

I'm not an expert in cross-continent interconnects, I have no idea what cables are being used there. I'd imagine that a lot of the backbone of the internet is fiber because that's what all the SRE memes say about wandering backhoes and sharks being the primary predator of fiber optic cables.

Re: Serving a high-performance blog solely from memory, using Rust

#65
post #55

Earlier quoted context omitted.

If they are keeping your article cached, what's the point of saying it's a high-performance blog? Saying it's slow because the CDN down means that it's just slow... You can have a 'high performance' blog run on a raspberry pi zero if it's globally cached by someone else, but then I wouldn't say that's high performance. Cool article though. Agree on the ructe part, and I dislike how whitespace is handled. I wish Jade/…

The blog itself is fast. The internet is the slow part.

I thought of a better way to phrase it. The website itself is fast, but the process of you observing the website is slow because of limitations of the speed of light (or other interconnects the internet uses to get your traffic to Helsinki).

Re: Serving a high-performance blog solely from memory, using Rust

#66
post #50

Earlier quoted context omitted.

The main thing the CDN provided was nodes on basically every continent that kept the site in cache. Without those servers on every continent keeping the site in cache, it takes longer to get to the netherlands to get the site loaded. The speed of light is only so fast.

> The speed of light is only so fast. Is the Internet not connected internationally (US -> Europe for example) via cables underneath the ocean? Speed of light would be satellite, light? Not electric current? Or is electricity flowing through a wire also "speed of light"?

These cables are fiber optics, but either way, the speed of light is still a bound.

Re: Serving a high-performance blog solely from memory, using Rust

#67
post #50

Earlier quoted context omitted.

The main thing the CDN provided was nodes on basically every continent that kept the site in cache. Without those servers on every continent keeping the site in cache, it takes longer to get to the netherlands to get the site loaded. The speed of light is only so fast.

> The speed of light is only so fast. Is the Internet not connected internationally (US -> Europe for example) via cables underneath the ocean? Speed of light would be satellite, light? Not electric current? Or is electricity flowing through a wire also "speed of light"?

Most (all?) Intercontinental cables will be fibre optic. So it's the speed of light (in glass, not a vacuum)

Re: Serving a high-performance blog solely from memory, using Rust

#68

I want to see this taken to the logical extreme. A real OS with actual drivers (no unikernel, no virtio) for a small set of hardware that only serves static pages. No need for virtual memory. Just hardcode the blog posts right into the OS and use the most minimal TCP stack you can make.

I think that should be possible with Cosmopolitan Rust (https://ahgamut.github.io/2022/07/27/ape-rust-example/). It would create a Baremetal runnable ELF binary with just cosmopolitan libc statically linked, not sure about driver support though.

Re: Serving a high-performance blog solely from memory, using Rust

#69

The tech is cool, but some of the language is so cringy. For example, the statement "websites are social constructs" makes zero sense. You could say that websites are material objects of a symbolic network of computer languages, like physical paper money is a material, fetishized object of the social construct of money. Websites themselves are not constructed socially. Maybe the author means how websites are perceive…

[deleted]

Re: Serving a high-performance blog solely from memory, using Rust

#70
post #50

Earlier quoted context omitted.

The main thing the CDN provided was nodes on basically every continent that kept the site in cache. Without those servers on every continent keeping the site in cache, it takes longer to get to the netherlands to get the site loaded. The speed of light is only so fast.

> The speed of light is only so fast. Is the Internet not connected internationally (US -> Europe for example) via cables underneath the ocean? Speed of light would be satellite, light? Not electric current? Or is electricity flowing through a wire also "speed of light"?

First of all, the "speed of light" is usually referring to c, the maximum speed that matter or energy can move at.

Second of all, electrical signals in cables move at speeds slightly lower than c, but very close to it, so the speed of light is still a very good approximation of the possible upper bound.

Third of all, intercontinental cables are normally fiber optic, for several reasons. That is, they directly transmit light through the cable.

Fourth, it should be noted that electricity is actually the same thing as light, since photons are the carrier particles of the electric field (when two charged particles interact, they are actually exchanging a photon). It's of course not visible light, but satellite communication also uses radio waves normally, which are not visible light either.

Finally, either through cables or through satellite communication, the distance/c minimum theoretical one-way latency is usually a significant under-estimation of the actually possible minimal latency, since the straight-line distance is significantly shorter than the actual cable/satellite-and-back distance that the signals must travel - the difference in straight-line VS physical path distance is typically much larger than the difference between the theoretical speed of light and the actual speed of the electrical signal propagation.

Post reply on HN