> i.e.: writing your own memory allocator for custom pools knowing exactly the latency, throughput, assembly generated for it. If you want to do this, you can

> i.e.: writing your own memory allocator for custom pools knowing exactly the latency, throughput, assembly generated for it. If you want to do this, you can gain a lot of performance with having custom allocators and pools on the JVM as well. E.g. frameworks like Netty have pooling strategies for ByteBuffers. If you go that route, you can also gain a lot of performance on the JVM, might really be competitive. Unfortunately the JVM still enforces too many heap allocations since value-types are not a thing yet, but it still performs well. One of interesting things I discovered about C++/Rust vs C#/Java is that the former language family wants you to do a lot of optimizations upfront, wich typically results in good performance. But sometimes you also spend too much time into optimizing something something that won't matter in practice. Whereas the managed languages are a bit easier to work with by default, but will thereby only yield mediocre performance. However you still have the chance to look into the bottlenecks and improve them by large margins using the right approaches. In C# now even more so than in Java thanks to tools like Span and value types.