Live data from Hacker News

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

xeiaso.net

51–60 of 143 posts

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

#51

Earlier quoted context omitted.

Quoted post unavailable.

> see if you find any "forbidden thoughts" As always, Venn diagram of "people with extremely pointless gripes about the Rust language" and "people who compare the slightest criticism to being accused of thoughtcrime" is a circle. That's not to say everyone who dislikes Rust is like this. I have plenty of gripes about Rust. Just the people who say things like "if you use a refcount and make a cycle, you can leak memor…

errr ... say what?

not a zinger this time (no zig for you!).

anyhoo, ciao.

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

#52

Earlier quoted context omitted.

Quoted post unavailable.

> see if you find any "forbidden thoughts" As always, Venn diagram of "people with extremely pointless gripes about the Rust language" and "people who compare the slightest criticism to being accused of thoughtcrime" is a circle. That's not to say everyone who dislikes Rust is like this. I have plenty of gripes about Rust. Just the people who say things like "if you use a refcount and make a cycle, you can leak memor…

Some seem to interpret the very existence of other people's ideas and especially what they perceive as an emerging consensus as a threat to their autonomy? I don't understand but I do observe it. I feel like what people actually take issue with is the existence of Rust and with people talking about it, and so they complain about how often it's on the front page, or they'll complain that it's in the title of the post, etc. But I feel like the root cause here is that they want it to go away, because it's existence bothers them.

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

#53
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.

And probably more importantly, routing packets through international traffic all the way to the Netherlands takes a while too.

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

#54
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.

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/Pug templates could be done in rust but will check out Maud.

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

#55
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.

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.

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

#56
post #44

Earlier quoted context omitted.

It's pretty bad faith to post an inflammatory comment, initially with several errors like referring to the Ref stuct instead of Rc , add edits to complain about downvotes, and then steadily edit it to be more correct and reasonable while leaving in the complaints about downvotes. Leaving the impression that it was the current iteration that attracted the downvotes because "the truth hurts". It suggests to me you know…

Quoted post unavailable.

> until you need cyclic references and have to use Rc or Refcell which means you can have memleaks.

Memory leaks are not unsafe.

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

#57
post #2

How can it be faster than a static page that is already in memory, the bytes are there you just send them over a socket? Transforming some template to rust code back to string buffer is somehow faster?

Well for one it's not static lol. I don't think they're claiming it's faster than a static website, are they?

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

#58
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 perceived, or conventions of web tech itself, is constructed socially?

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

#59
post #20

Earlier quoted context omitted.

That “traditional” site doesn’t actually load the data from disk, in practice. It does once, after a reboot, but that’s true for this solution’s executable file as well.

That “traditional” site doesn’t actually load the data from disk, in practice. It does once, after a reboot, but that’s true for this solution’s executable file as well. Does Apache/Nginx/IIS load static files in memory ahead of time? I would assume no, unless someone went through and did some optimizations. Even so, there is always a point where memory runs out, and in that case a templating engine is essentially co…

With Apache/Nginx e.t.c. a file is cached by VM/FS on the first request and will stay in RAM for a long time unless there is a memory pressure. For most sites this is good enough. For cases where it isn't one can pre-load files after a reboot using find /path -type f -exec cat {} + > /dev/null.

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

#60
post #20

Earlier quoted context omitted.

That “traditional” site doesn’t actually load the data from disk, in practice. It does once, after a reboot, but that’s true for this solution’s executable file as well.

That “traditional” site doesn’t actually load the data from disk, in practice. It does once, after a reboot, but that’s true for this solution’s executable file as well. Does Apache/Nginx/IIS load static files in memory ahead of time? I would assume no, unless someone went through and did some optimizations. Even so, there is always a point where memory runs out, and in that case a templating engine is essentially co…

Author here. I don't identify as male. It would be nice if you could update your comment to not make a factual error when referring to me. Please use https://pronoun.is/they.

Thanks!

Post reply on HN