4 ms·
Wow, that sounds like fun. What exactly is in the LinkedIn stack that requires so much memory?
by davedx 14y ago
Wow, that sounds like fun. What exactly is in the LinkedIn stack that requires so much memory?
- ucho 14y agoNowadays I get OOM while running only FireFox and Netbeans - and I am not even running software I develop on my box :P
- brown9-2 14y agoSpeculation, but it sounds like the main webapp you see at linkedin.com is a single monolithic application.
- flatline3 14y agoEven if it is a single monolithic application, it in no way could explain the use of that much RAM.
- joshhart 14y agoSystems actually come standard with 48 gigs :) As it turns out, that's really useful for the part of my job requiring data modeling. Somebody suggested LinkedIn is one large application, which is absolutely false. It's composed of many small applications, each deployed as a WAR file since the non-Node.js part of the site is on the JVM. There's a lot of overhead that comes from deploying this way. It doesn't matter in production or staging, but it adds up on a desktop. At this point in time though, dev machines have stopped growing because we have shared stacks you can deploy a couple pieces of the application against if you want to test the whole thing.