Live data from Hacker News

LinkedIn uses 2.4 GB RAM across two tabs

news.ycombinator.com

401–410 of 481 posts

Re: LinkedIn uses 2.4 GB RAM across two tabs

#401
post #370

Let's be real, LinkedIn is full of LinkedIn Lunatics but pretty much all mainstream social media is pretty shit. They're just different flavors of shit. LinkedIn: bad. Facebook: bad. Twitter: I literally think it contributed to the collapse of discourse and rise of shallow thought / rejection of expertise. I'm not going to list more because the theme is, you guessed it, they're bad. Google+ had promise in that the ma…

> Google+ had promise No ads was a huge plus. Take away the financial incentive and you get rid of most of the worst behavior.

If you don't have adv from platform itself it doesn't mean that site content is not flooded by endless spammers content. LinkedIn is great example where you have both.

Re: LinkedIn uses 2.4 GB RAM across two tabs

#404

The juxtaposition between this and "Voyager 1 runs on 69 KB of memory and an 8-track tape recorder" is probably the best one I've seen in a long time

To be fair, Voyager 1 doesn't have to render 47 "congratulate your connection" notifications at the same time.

With autosuggestions to click so you don't even have to type anymore!

Re: LinkedIn uses 2.4 GB RAM across two tabs

#406
When I first saw the headline, I thought it was referring to the servers and thought, damn, that is impressive!

Then I realised that it was a bit too impressive.

The possibility that a website would use 2.4gb ram did not even occur to me. What is it even doing with all that memory?

For reference civilisation 4 is runnable with 2gb ram.

Re: LinkedIn uses 2.4 GB RAM across two tabs

#407
post #295

Earlier quoted context omitted.

A probe collecting data in space takes <70 kB of memory. I fail to see how this statement should make me feel happy

Space is mostly empty there is not much interesting stuff to collect and who’s going to buy that data LinkedIn on the other hand has user behavior, computer details etc. that’s a lot of interesting data.

>Space is mostly empty

Yes, but Space is big. Really big. You just won't believe how vastly, hugely, mind-bogglingly big it is. I mean, you may think it's a long way down the road to the chemist's, but that's just peanuts to space.

Re: LinkedIn uses 2.4 GB RAM across two tabs

#408

Earlier quoted context omitted.

As someone was pointing out in a thread the other day about memory usage, a lot is fonts and images. EDIT: Just mind boggling to get d/v'ed for pointing out voyager doesn't have to render fonts or images...

How much? You typically don't want more than a few different fonts on a given document. And neither fonts nor web images should be bigger than hundreds of kilobytes. How do we get to gigs?

I don't see mention of this in the discussion, so I will add: I think people also don't close tabs. And probably these LI tabs have been up for a long time. Maybe weeks or months.

I completely exit my web browser(s) at least 1x per day, and use bookmarks to get back to pages I need. As a result, I don't have issues with memory leaks or unbounded growth of RAM use. For me, its just the "proper" way to use a program like a web browser, but I'm old enough to be from the era that restarting programs and the OS could fix issues. I recognize that most people feel it is unreasonable to quit the browser, pretty much ever.

Re: LinkedIn uses 2.4 GB RAM across two tabs

#409

This is the part about the "wasm won't replace JavaScript" argument I see being slept on and why I am so disheartened about how practically no progress has been made on it. Most trivial apps don't need to be optimized, and for them, JavaScript is fine. But for complex interactive web applications - it really fuggin matters. Think; - vscode - facebook - jira - linkedin - reddit There's no reason these applications sho…

I realize this is not an orthodox view, but WASM won't make the typical user have a better experience.

I think it could improve Photopea, the various office suite programs, and perhaps unknown unknowns.

But, much more important than the uncertain is the current Web which will become less accessible and closed.

The ease in reverse engineering JavaScript has more than once shown negligence and malice by Website developers (one example is the recent Google scandal, where they were diminishing the user experience on competing browsers).

If I wanted to run trusted programs, I would have used native binaries.

Re: LinkedIn uses 2.4 GB RAM across two tabs

#410
post #245
post #113

Earlier quoted context omitted.

> Does anyone else have the feeling they run into this sort of thing more often of late? Simple pages with just text on it that take gigabytes (AWS), or pages that look simple but it takes your browser everything it has to render it at what looks like 22 fps? It is to do with websites essentially baking in their own browser written in javascript to track as much user behavior as possible.

Spot on. It's why I quit adtech in 2015. Running realtime auctions server-side is one thing, but building what basically amounts to live-feed screen capture ..

I do live-feed screen capture and it doesn't really consume much and is barely unnoticeable. Running 100 live-feed screen capture is a different story though.
Post reply on HN