Why low-latency Java still requires discipline?
theanonymousone
90 points
46 comments
July 06, 2026
Related Discussions
Found 5 related stories in 326.0ms across 14,015 title embeddings via pgvector HNSW
- Java is fast, code might not be siegers · 192 pts · March 20, 2026 · 59% similar
- Reading code instead of writing code: The underestimated senior discipline goloroden · 23 pts · May 16, 2026 · 48% similar
- Taming LLMs: Using Executable Oracles to Prevent Bad Code mad44 · 32 pts · March 26, 2026 · 45% similar
- Slow is smooth and smooth is fast: What software teams can learn from Navy SEALs goloroden · 12 pts · March 11, 2026 · 45% similar
- Ask HN: Will programmers write more efficient code during the memory shortage? amichail · 65 pts · June 19, 2026 · 45% similar
Discussion Highlights (7 comments)
dominicrose
page doesn't load "En attente de la réponse de chronicle.software."
motoboi
I found claude and GPT very helpful on this, because java have a very sofisticated monitoring harness. Just ask the agent to connect to the running application (on kubernetes or whatever) on prod and do a java flight recording then analyze allocations. I managed to improve some applications of ours from several garbage collections per second to several minutes between collections. That _really_ improves p99.
chuckadams
I get that blog posts often advertise a company's products, but this one had absolutely zero content other than advertising.
opentokix
How about not using Java? Then you can have low latency. Average go, rust, c++ and c will outperform amazing java programs, and the former will also be way way more easy to run, troubleshoot, interpret logs from. Java is usch garbage in every stack.
pjmlp
Even C requires discipline to write low latency code, if you think otherwise, you never used a profiler.
treyd
On mobile the whole page text is aligned center which makes it really hard to read.
sandeepkd
Had to write a router software once in Java back in 2014. The past experience in me believed that its not a good choice to use something with stop the world GCs for routers. The goal was to have everything under 1ms (max 2ms in rare cases). It has http server on head and websocket connections on the tail end. Turns out the class instantiations and JSON parsing were a bottleneck. Thread safe resources were valuable, the libraries which did not had thread safe resources were re-written to support what we needed. The http server was re-written barebones, the JSON parsing was re-written with barebones. And it worked.