News for hackers. Stuff that matters.

A comment on Rust vs C Pitfalls. Parent comment

Re:Rust vs C Pitfalls by fpoling on Wednesday December 28, 2016 @06:48AM (#13269929)
In some cases those HFT installations are tuned not to run full Java GC within 8 hours during the trading day. Then they are rebooted.
[ Parent | on HN ]
Re:Rust vs C Pitfalls by njs12345 on Wednesday December 28, 2016 @08:25AM (#13270301)
That sounds interesting - have you got any more details on exactly how they set this up?
[ Parent | on HN ]
Re:Rust vs C Pitfalls by gravypod on Wednesday December 28, 2016 @09:00AM (#13270469)
You can also use the Java Unsafe class to squeeze performance (every last bit) by recycling objects. I'm sad to say that I've had to do that at least once to make some vector math work.

Edit: Check out https://dzone.com/articles/understanding-sunmiscunsafe

[ Parent | on HN ]
Re:Rust vs C Pitfalls by fpoling on Wednesday December 28, 2016 @10:32AM (#13271094)
A person on a conference has not mentioned details. The reason for Java is productivity and access to a bigger pool of developers.
[ Parent | on HN ]