3 ms·
You start by congratulating yourself for refusing to buy into the Java hype, then continue on with business as usual in C++ or some other non-garbage-collected
by marssaxman 11y ago
You start by congratulating yourself for refusing to buy into the Java hype, then continue on with business as usual in C++ or some other non-garbage-collected language.
- vardump 11y agoAfter that you discover it's a NUMA machine, you have a lot of inter-cpu communication and curse you have no GC. Why? Because you bottleneck inter-cpu communication so easily with object synchronization. With GC quite a bit of it can be avoided. If Java just didn't need to allocate each damn small value object (think struct) separately, I think it'd be a lot better with large heaps. Array of 1000 non-elementary values could be just one allocation, not 1001. That'd also be 1000 times faster to garbage collect.
- RandomBK 11y agoWe're getting this soon(ish)! http://openjdk.java.net/jeps/169 http://openjdk.java.net/jeps/169 Still a few years behind other languages, but its coming...
- pron 11y agoQuite the opposite. The only way to use so much RAM is with lots and lots of threads (running on lots and lots of cores), which means either sharding or sharing. Sharding scales really badly because when you do have cross-shard transactions or queries, you need expensive locks. A GC makes general-purpose, high-performance lock-free data structures much, much, much easier.