3 ms·

I'd like to see an independent check of this claim, like 50% memory reduction, but under what circumstances? If that's at startup when the app doesn't consume

I'd like to see an independent check of this claim, like 50% memory reduction, but under what circumstances? If that's at startup when the app doesn't consume a huge amount of memory that's not a particularly interesting claim. If that's after hours of app usage when the previous Electron app used to consume let's say 1GB that's really impressive, but if the app is consuming 1GB of memory it's because the app itself is allocating a huge amount of stuff in the heap, you can't just swap browser engine under the hood and cut that in half with no downsides, otherwise every browser maker would do just that.

hulitu 5y ago
> I'd like to see an independent check of this claim, like 50% memory reduction, but under what circumstances? You have 32 GB RAM ? Teams will use only 16 GB. > If that's at startup when the app doesn't consume a huge amount of memory that's not a particularly interesting claim. Of course it's at startup. Then the app needs to draw its ugly black window and it needs more RAM. It uses HW acceleration, you know. And it's slow like hell. > If that's after hours of app usage when the previous Electron app used to consume let's say 1GB that's really impressive, but if the app is consuming 1GB of memory it's because the app itself is allocating a huge amount of stuff in the heap, you can't just swap browser engine under the hood and cut that in half with no downsides, otherwise every browser maker would do just that. Every respectable browser will use the whole available memory. From time to time they will have a patch to halve the memory usage but they will recover quickly.