HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
diracdeltas
FastestWebsiteEver
C2017–2021
diracdeltas / FastestWebsiteEver

FastestWebsiteEver

ultrafast single TCP packet audio/visual experience

6Distinct people
6Mentions
0Explicit recommenders
1.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

ultrafast single TCP packet audio/visual experience

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year6 dated mentions

Observed mentions: 2017-05-15 01:26:55 UTC to 2021-08-08 15:10:58 UTC.

0122017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC220
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202

What Hacker News says

6 sources
That's interesting, but #1 seems like a bug in your shared hosting service. 20 seconds for a single request isn't even usable, and an unoptimized Django config doesn't start anywhere near that slow. A $5 Linode and stock Django should be able to get you the 500-1000ms. Also, I'm not sure how you're measuring 250 us, but I doubt it's meaningful number, because in practice either of these two numbers will be greater than that: 1) The network latency to send as single packet from the user to your server. This is usually more like 10 ms, or 40x what you're quoting. Great link I saw on lobste.rs -- a website in a SINGLE PACKET: https://github.com/diracdeltas/FastestWebsiteEver 2) The time it takes the browser to render the page (e.g. loaded from the memory of a local server). Static HTML might render in 250 microseconds, but I doubt that an
Read the rest
ything with JavaScript or even CSS will. In other words, I highly doubt you have 250 us end-user latency; it's basically impossible with the web and "normal conditions". You can choose to measure it in some weird way, but it doesn't reflect what your users are experiencing. EDIT: I guess if you throw out the connection time, 250 us possible. But I don't think it's meaningful to throw out the connection time -- you at least have to average it over many requests.
In Tips for Application Performance (2015)

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.