b_llc

5 ms·

1.
by b_llc 1y ago
I'd like to thank everyone for the feedback. I'm going to reflect on the feedback, rewrite the article with better explanations of the problem domain, and its limitations. I've clearly failed to articulate the core capability
2.
by b_llc 1y ago
The code is 100% mine. The architecture and code evolved over 5-years as Axon adapted for a number of projects. I started to revamp the project 2-3 weeks ago. Throughout that process, I used Claude to check for logical errors and simplifica
3.
by b_llc 1y ago
You're right about boundary caching opportunities. The computational cost I'm referring to comes from the construction of the per-request multipart header, and file metadata operations, rather than just boundary generation. The &q
4.
by b_llc 1y ago
I might be wrong then! I'll make a note to take a look. Thanks for pointing this out.
5.
by b_llc 1y ago
Axon generates dynamic multipart responses with boundaries and headers to bundle files specified via query parameters. sendfile handles "serve this specific file" but does not handle "bundle these N files into a multipart res
6.
by b_llc 1y ago
You're right - this represents computational duress, not optimal efficiency. The 1 CPU struggles to handle the 50 concurrent user scenario and was chosen to demonstrate worst-case behavior rather than peak performance. I intended to st
7.
by b_llc 1y ago
By I/O limits, I meant network bandwidth and disk throughput limits, not memory capacity. Thanks for pointing out the ambiguity.
8.
by b_llc 1y ago
Good question! Yes, CPU saturation is the desired behavior here. The multipart streaming workload is inherently expensive. The cost of generating boundaries and constructing headers scales with request count and payload size. The architectu
9.
Show HN: Python file streaming 237MB/s on $8/M droplet in 507 lines of stdlib(bellone.com)
21 points by b_llc 1y ago|16 comments
10.
Ask HN: Interested in a Flask-Like App with HTTP/3 Multiplexing and Streaming?
2 points by b_llc 2y ago|0 comments