News for hackers. Stuff that matters.
Re:Modern garbage collection by twic on Tuesday December 20, 2016 @09:36AM (#13220097)
Hmm, well if the processing is microservices, presumably the data is in a NoSQL database.

More seriously, though, isn't most large in-memory data storage done off the garbage collected heap? I have to confess i'm actually not sure what anyone is doing with >20 GB of normal objects.

Re:Modern garbage collection by sheeshkebab on Tuesday December 20, 2016 @02:12PM (#13222917)
Search (elastic/solr), Cassandra, presto, and most other java backend storage and data processing engines need 20+Gb (at least) to be mildly useful. It's not uncommong to go with 64gb+ heaps there too.

Microservices/API won't help with lowering these.

Re:Modern garbage collection by osi on Tuesday December 20, 2016 @03:51PM (#13223814)
yes, exactly this. and by having scalable GC algos so you don't need to do "off heap" tricks in java, things are much easier.
Re:Modern garbage collection by dkersten on Tuesday December 20, 2016 @11:33AM (#13221320)
I'm sure people do use huge heaps, but most web applications I know of (microservice or not) store the bulk of their data in a (separate) database. So, unless your application is a database, which might want a huge heap so it can cache a lot in-memory, I don't think huge heaps are really necessary. IMHO, at least.
Re:Modern garbage collection by dom0 on Tuesday December 20, 2016 @12:38PM (#13221987)
Since it's not really possible to do reliable giant user space caches in the POSIX model of things you'd usually delegate to the page cache.