Isn't this mostly about java cold start costs? It might be that other people are optimizing for steady-state performance, not transient startup performance.
Java is almost always significantly faster than Go because the Go runtime does a poor job of exploiting large memory page, doesn't support text-on-huge-pages, and barely supports profile-guided optimization. With HotSpot you get all of this and more for free. Go is fine but Java is peak.
This would have different answers depending on if it ran on a machine with a more closely-shared cache, right? For example on an Intel efficiency core cluster where 4 cores share an L2.
Reading the clock every time you jump into a closure is in fact incredibly wasteful, and is exacerbated by chopping work up into tiny chunks for questionable reasons.
The difference is nobody in the C++ community believes that a dominant asynchronous executor library exists, and there is not a pervasive belief that it would be helpful.
I'm just reporting from the trenches here. I think you are suggesting that everyone is aware of and capable of using state-of-the-art (from 20 years ago) tracing schemes like XRay[1], when in reality they are not. Most projects would be well-served by any basic profiler but even profiling is apparently for wizards, because I've seen a lot of projects that will resort to manually annotating functions with OTel trace spans, which are ~millions of times more expensive than function calls. Even eBPF uprobe/uretprobe is 100x more expensive than XRay, at a minimum. HotSpot's JFR is like a miracle compared to what people suffer through to diagnose Rust+Tokio.
I can get an LLM to trace my incomprehensible Tokio application which was also written by an LLM, which is why I don't understand its behavior. Truly the future we were promised.
Also a great way to make sure that your app spends most of its time in observability overhead. For example even the latency histogram that the OP mentions is wildly expensive.
All of the significant server applications I have encountered in the industry have suffered from the same problem, which surprised their authors but seemed obvious to me: the application was spending the majority of its CPU time doing meta-work like entering and leaving epoll, stealing work from itself, etc. There are principles for writing Tokio servers and these are good points in the OP but I think they are little-known and too easy to violate.
Reporting bugs before Ubuntu releases has never worked for me. They always land a bunch of major changes after the supposed "freeze" then they ignore all feedback because of the freeze. It's infuriating.
Lol no. For almost the entire 20th century, until 1992, Filipinos could just join the Navy or Coast Guard at foreign recruiting posts, without even being American residents, then get fast-tracked for citizenship.
For the same reason that foreign nationals can join the military, including the Coast Guard that has an overlapping mission: it's a nation of immigrants and for centuries until very recently most Americans readily recognized the value and necessity of recruiting foreign people into various posts.
Some aspects of Prop. 103 work. The definition of "good driver" as everyone who hasn't caused a fatality in the last 3 years is not one of those aspects.
> In-car dongles that track jerky driving, crash event recorders, and driver monitoring systems now let an insurer observe behavior directly and price it.
Uh, but not in California, because of 1988's Prop. 103. Telematics for insurance pricing are completely unavailable in California.
Mine has been strictly MRU forever. When I look at this video, it does not resemble the software on my LG OLED TV at all. There must be several platforms or generations.
It feels like there must be multiple completely different implementations of LG OLED TVs. I would not say that my LG has a "main screen" of any kind. When I turn mine on it shows the last input that had been used or, if that thing is off, it shows the bouncy egg and "No Signal". If I press the button on the remote that says RECENTS and has a picture of a house on it, which I guess is the "main screen", it maintains the bouncy egg but shows a ribbon of apps on the bottom. Those are my installed apps: Hulu, Prime, Peacock, YouTube, Netflix, Apple TV, and Disney+ happen to be today's recents. Where is this "main screen" where unbidden appvertisements arise?
This is almost unreadable. The "papers" are never referenced anywhere, so the claims being refuted cannot be evaluated. The whole fact of the TTL doesn't seem relevant at all. There are many, many well-researched admission and eviction policies that this readme doesn't mention. I just don't get why we are reading this.
Your statement about SSD availability and performance does not fit with my personal recollections of history. Smoking fast SSDs were completely vanilla items you could order from anyone in 2015. For example, the Intel DC P35/6/700 series. Each of these was as good as 25 HDDs for linear reads and more like 5000 HDDs for random reads. The U.2 specification for putting SSDs in boxes was formalized in 2011. Outside of the mass market, cloud builders had private SSD designs long before 2015.