> We ended up running the code through profiler on our CI system which would fail the build if it detected any potential paths of GC. Object pools and flyweights everywhere
Pretty standard practice in HFT Java, but the GP correctly points out this is not idiomatic Java.
> In other words, it’s possible to write Java, from the machine level on up, for low latency. You just need to write it like C++, with memory management in mind at each stage of development.
Pretty standard practice in HFT Java, but the GP correctly points out this is not idiomatic Java.