4 ms·
Interested to know what workloads are using multi-TB heap sizes? Largest I've used has only been in the 48-64GB size and even then it seemed like a waste.
by stuff4ben 8y ago
Interested to know what workloads are using multi-TB heap sizes? Largest I've used has only been in the 48-64GB size and even then it seemed like a waste.
- pjmlp 8y agoI have only heard about it in the context of Fintech, where they keep all transaction data around. At least they seem to be Azul´s biggest customer base.
- kjeetgill 8y ago1.2 TB Xmx (Java heap) here, reporting in from LinkedIn not fintech. Basically, graphs are hard to shard ... what if we didn't bother? You can query an in memory graph pretty quickly out into the 2nd or 3rd degree. Even G1 (untuned) only pauses for 250ms once every few minuets. It's not perfect but good enough to ignore.
- hermitdev 8y ago250ms is atrocious for finance. Need a small handful of microseconds to not be noticed.
- kjeetgill 8y agoOf course. But this is with zero tuning in place. This is just what the default G1 gets you on that heap size. I'm sure with 2 or 3 flags we could bring that down easily. Given how infrequently we're seeing them (one every few minutes) it's fine for what we're doing.
- repolfx 8y agoWell G1's default pause time goal is 100msec so it won't even try to do better than that without 'tuning' (telling it to pause for less time).