3 ms·

I've recently installed Visual Studio for the first time and it uses up 3-5% CPU while doing nothing. It takes an age to load. It uses heaps of RAM with no proj

I've recently installed Visual Studio for the first time and it uses up 3-5% CPU while doing nothing. It takes an age to load. It uses heaps of RAM with no projects open. I'm not sure if VS is also Electron but it's another black mark against Microsoft either way. I beg to differ on Electron: I have never seen a single use of it where it doesn't use an extraordinary amount of RAM and there mere concept of using an embedded web site browser for a GUI is simply an unacceptable thought, let alone a realisation of modern-day software. It should have never have happened.

pizza234 5y ago
> it uses up 3-5% CPU while doing nothing This is meaningless without context, as editors typically run indexing processes in the background. I used to use $beloved_native_editor, which in some cases ran at 100% single-thread for extended amounts of time (due to indexing). > It takes an age to load. It uses heaps of RAM with no projects open [...] I have never seen a single use of it where it doesn't use an extraordinary amount of RAM I've taken some real-world measurements, with the disclaimer there is no universal interpretation of measuring memory: > Private + Shared = RAM used > > 8.9 MiB + 9.1 MiB = 18.0 MiB > 17.0 MiB + 17.3 MiB = 34.3 MiB > 119.2 MiB + 149.4 MiB = 268.6 MiB > --------------------------------- > 321.0 MiB > ================================= > Private + Shared = RAM used > > 332.1 MiB + 519.2 MiB = 851.3 MiB > --------------------------------- > 851.3 MiB > ================================= > Private + Shared = RAM used > > 124.0 KiB + 176.0 KiB = 300.0 KiB > 1.1 MiB + 1.1 MiB = 2.1 MiB > 95.5 MiB + 200.2 MiB = 295.6 MiB > 1.3 GiB + 1.3 GiB = 2.5 GiB > --------------------------------- > 2.8 GiB > ================================= Startup times (approximate), before being able to type: 0.3", 1.2", 4.7". The editors are vanilla installations, and I've opened the directory of a relatively large project. The machine is a modern desktop one. The editor that people love to hate is not the one you'd expect.

pizza234 5y ago

> it uses up 3-5% CPU while doing nothing This is meaningless without context, as editors typically run indexing processes in the background. I used to use $beloved_native_editor, which in some cases ran at 100% single-thread for extended amounts of time (due to indexing). > It takes an age to load. It uses heaps of RAM with no projects open [...] I have never seen a single use of it where it doesn't use an extraordinary amount of RAM I've taken some real-world measurements, with the disclaimer there is no universal interpretation of measuring memory: > Private + Shared = RAM used > > 8.9 MiB + 9.1 MiB = 18.0 MiB > 17.0 MiB + 17.3 MiB = 34.3 MiB > 119.2 MiB + 149.4 MiB = 268.6 MiB > --------------------------------- > 321.0 MiB > ================================= > Private + Shared = RAM used > > 332.1 MiB + 519.2 MiB = 851.3 MiB > --------------------------------- > 851.3 MiB > ================================= > Private + Shared = RAM used > > 124.0 KiB + 176.0 KiB = 300.0 KiB > 1.1 MiB + 1.1 MiB = 2.1 MiB > 95.5 MiB + 200.2 MiB = 295.6 MiB > 1.3 GiB + 1.3 GiB = 2.5 GiB > --------------------------------- > 2.8 GiB > ================================= Startup times (approximate), before being able to type: 0.3", 1.2", 4.7". The editors are vanilla installations, and I've opened the directory of a relatively large project. The machine is a modern desktop one. The editor that people love to hate is not the one you'd expect.