Hacker News Reader

To add to this, I know for a fact some people who are really serious about Java + HFT, and they would never ever use a GC. I can’t believe how much this article talks about Zing and other GCs, while the de-facto standard way of doing this is to just always reuse all objects and never deallocate them.

I get a very real feeling that the people writing this article have no idea what they’re talking about.

View on HN

How do you do that? Even when your code has no memory allocations sockets still leak memory.

You use special libraries designed for this purpose, that use a static buffer under the hood themselves. Or you just make sure that memory usage increase is low enough that it isn’t a problem. You sometimes have places where they do for example one GC call a day.

Take a look at https://github.com/OpenHFT to get a taste of what Java + HFT looks like.

Reply on news.ycombinator.com