Why low-latency Java still requires discipline?
chronicle.software
Why low-latency Java still requires discipline?
1–10 of 56 posts
Re: Why low-latency Java still requires discipline?
#2page doesn't load "En attente de la réponse de chronicle.software."
Re: Why low-latency Java still requires discipline?
#3page doesn't load "En attente de la réponse de chronicle.software."
+ low latency anything requires discipline. if you lose 5ms you can't get it back.
Re: Why low-latency Java still requires discipline?
#4I 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.
Re: Why low-latency Java still requires discipline?
#5I get that blog posts often advertise a company's products, but this one had absolutely zero content other than advertising.
Re: Why low-latency Java still requires discipline?
#6I 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.
[dead]
Re: Why low-latency Java still requires discipline?
#7How 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.
Re: Why low-latency Java still requires discipline?
#8How 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.
yes, until you need debugging.
Re: Why low-latency Java still requires discipline?
#9How 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.
Rust? OK.
C++ or go? Then you'll have to take a very closer look, because the java JIT is wonderful. A masterpiece of several hands, actually.
Re: Why low-latency Java still requires discipline?
#10Even C requires discipline to write low latency code, if you think otherwise, you never used a profiler.