Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A super fast website using Cloudflare workers

crazyfast.website

Post reply on HN
Print view View original

61–70 of 83 posts

Re: A super fast website using Cloudflare workers

#61

Post by elcritch »

usrnm wrote: post #6
Terretta wrote: post #2

Speed: 74ms 241ms … LOL … These 30 ms and 4 ms numbers were typical Apache to Netscape from MAE East and MAE West in 1998. Twenty five years and orders of magnitude more computing later? Same numbers.

I know, right? Almost 30 years and no progress in the speed of light? What are all these engineers even doing?

I believe that FTL communication (if it's achievable) will start out in data centers at small scales. Perhaps millimeters.

Possibly as an extension of Quantum Computing where some probabilistic asymmetry can be taken advantage of. The QC itself might not be faster than classical computing, but the FTL comms could improve memory and cache access.

Also MetaGoog will use it to serve up hyper personalized ads in their Gemini based Metaverse.

Re: A super fast website using Cloudflare workers

#62

Post by ComputerGuru »

oefrha wrote: post #18

> ~2.5KB Brotli Smaller than most images. Brotli is so 2024. Use zstd. (73.62%, I know. Slightly worse compression ratio, I know that too.)

Do browsers use a custom dictionary for zstd (I don’t think so since I can precompress zstd content server-side)?

Brotli was designed for html compression so despite/while being a relatively inferior algorithm, its stock dictionary is all html/css/js-trained/optimized. Chrome/Blink recently added support for seeing content compressed with a bespoke dictionary, but that only works for massive sites that have a heavily skewed new/returning visit ratio (because of the cost of shipping both the compressed content and the dictionary).

Long story short, I could see br being better than zstd for basic web purposes.

Re: A super fast website using Cloudflare workers

#63

Post by a456463 »

onion2k wrote: post #46

Getting a site to load quickly isn't that difficult from a technical perspective. You just need to strip out everything that slows it down. If you can deliver a page of HTML and inlined CSS that renders without JS or images then your site will be fast (or at least it'll be perceived as fast, which is fine.) So long as you're using some fairly reputable hosting infrastructure (AWS, Azure, Google, etc), and if you're r…

Exactly. My site loads fast with no images causes it is a demo site. Sure Jan!

Re: A super fast website using Cloudflare workers

#64

Post by coherentpony »

davidmurdoch wrote: post #7
Terretta wrote: post #2

Speed: 74ms 241ms … LOL … These 30 ms and 4 ms numbers were typical Apache to Netscape from MAE East and MAE West in 1998. Twenty five years and orders of magnitude more computing later? Same numbers.

But now it's that fast from almost everywhere on the planet, with nearly zero effort from the developer. We've been limited by light speed here, not compute.

The circumference of Earth at the equator is about 40,000 km and the speed of light is about 300,000 km/s. The appropriate division results in about 0.13 s.

That seems to track. The vast majority of requests won’t go half way around the Earth, so maybe halving that time at 0.06 seems like a reasonable target.

Re: A super fast website using Cloudflare workers

#65

Post by jonathanstrange »

PunchyHamster wrote: post #14

One time I decided to check how much faster really you can go while still getting decent usability out of "simple blog platform" type of webapp. End result, written in go, did around 80-200us to generate post page and 150-200us (on cheap linode VPS... probably far faster on my dev machine) for index page with a bunch of posts. Core was basically * pre-compile the templates * load blogpost into RAM, pre-compile and ca…

I had my page served with Go and it was instant, 100% speed score. Then I moved the static content to a CDN and it's slower now, only 96% speed. However, the question is really how fast the page is when it comes under heavy load.

Re: A super fast website using Cloudflare workers

#66

Post by skydhash »

onion2k wrote: post #60
skydhash wrote: post #52

Earlier quoted context omitted.

> Eventually you'll want to know what users are doing, and specifically why they're not doing what you expected them to do after you spent ages crafting the perfect user journeys around your app That's putting the cart before the horse. The way it's properly done is just to invite a few users and measure and track their interaction with your software. And this way you'd have good feedback instead of frustrating your…

Yeah, you'll do that, and get great feedback, and then when you roll it out to other users they'll do weird stuff you've not seen any of the test group try before. Users being weird are the fundamental root cause of all software problems. :)

Users can’t click a button that does not exist. It’s on product and engineering to curtail what the user can do. Optimizing for the happy path while not eliminating the incorrect flow is just bad software engineering.

Re: A super fast website using Cloudflare workers

#68

Post by bryanrasmussen »

hmm, it seems the last static site I did is slightly faster https://nissestyrelsen.dk/ but probably just because it's hosted in country near me, if I was somewhere else probably much worse. Not that I care that much to really research it, I figure it's fast enough and just a funny idea.

Re: A super fast website using Cloudflare workers

#69

Post by bryanrasmussen »

bryanrasmussen wrote: post #68

hmm, it seems the last static site I did is slightly faster https://nissestyrelsen.dk/ but probably just because it's hosted in country near me, if I was somewhere else probably much worse. Not that I care that much to really research it, I figure it's fast enough and just a funny idea.

my luck HN gonna crash it.
Post reply on HN