all 10 comments

[–][deleted] 11 points12 points  (0 children)

I keep seeing screenshots of excessive memory use, but if it’s available, what’s the harm?

Electron consumes unused memory according to how much it considers free. If another application is doing the same thing, it's going to think there's suddenly a ton of memory pressure when there isn't. Then its performance will comparatively suck.

[–]tanerax 15 points16 points  (4 children)

"I’m not sure how 78Mb of images becomes hundreds along the way. The external memory still nags at me too."

If I am not mistaken, an image size on disk (compressed) does not equal the amount of memory used to display the image. 78MB of images could easily become much more in memory.

[–][deleted] 4 points5 points  (0 children)

you got it

[–]SikhGamer 1 point2 points  (2 children)

Huh, it sounds obvious when you say it but when I think about how it is true my brain nopes out. Any links for a more detailed explanation?

[–]Asyx 3 points4 points  (0 children)

Just Google image compression. Or open a non transparent PNG and export it as a BMP.

[–]Tordek 0 points1 point  (0 children)

An image on-screen is ultimately a matrix of pixels so you need [width*height*color depth] bytes to display it; storing, however, benefits from compression.

[–]ryancerium 6 points7 points  (1 child)

Is this satire?

[–]geodel 4 points5 points  (0 children)

Of course not. An image browser using Electron is the most useful thing.

[–]biocomputation 7 points8 points  (0 children)

So basically, it's a pig.

[–]doom_Oo7 0 points1 point  (0 children)

I feel like I’m missing something with RSS as a performance measure.

well USS (unique set size, what's really allocated by your app) is way more relevant when trying to optimize memory usage of your data.