4 ms·
Wow! Multi-terabyte heaps? That sounds like way to much stuff in memory. When would you need multiple terabytes in RAM? I mean come on... What kind of applicati
by ateesdalejr 9y ago
Wow! Multi-terabyte heaps? That sounds like way to much stuff in memory. When would you need multiple terabytes in RAM? I mean come on... What kind of application even needs that. Though I do admit that javascript needs this kind of GC implementation because the hangs JS causes are a real pain.
- rand0mthought 9y agoRun Apache Spark on the box with 256+ GB of RAM. The GC stalls by 60 or more seconds are quite typical for heavy queries. I hope new GC will bring improvements.
- jerdavis 9y agoFor Spark/etc I only care about throughput. It can stall all it wants. Exception (possibly) being spark streaming.
- dkersten 9y agoAnalytics jobs, some database use cases, machine learning, simulation... plenty of things could make use of huge heaps.
- ksec 9y agoAnd TB memory is merely enough for lots these use case. We can now skip a lot of complicated scaling issues with merely a few boxes. The problem is memory price / GB not only hasn't gone down but goes up.
- hinkley 9y agoMulti terabyte heaps would move the bar for Big Data way to the right and let most of us just ignore the whole thing. Basic space versus time trade off. In eight years we’ll laugh about how stupid people were for doing it, and in another 8 laughing at the people who didn’t. One of the reasons things like memcache became a thing is because we hit a point where same-switch tcp/ip round trips were smaller than average seek time for your hard drives. I gotta say, it’s a little crazy that it was faster to ask another machine a question than to look it up yourself, but there it is.