3 ms·

As a side note, GMail memory usage has improved vastly (probably because it was monstruous to begin with). Years ago my GMail tab consumed almost 500 Mb, but no

As a side note, GMail memory usage has improved vastly (probably because it was monstruous to begin with). Years ago my GMail tab consumed almost 500 Mb, but nowadays it uses less than 100, with my same usage patterns.

mayli 6y ago
300MB onload, dropped to 240MB after idling for few minutes. Are you sure it's using less than 100MB? in comparison with the post, it takes about 500MB ram, which is weird for such simple webpage. This HN page takes 40MB.
- ASalazarMX 6y ago
  Oh sorry, I measured it on Firefox. Chrome on Linux started at 160 Mb, and it settled around 150. I've disabled Hangouts, and the right sidebar, so that might account for the differences. Funny how Firefox reports a third of that, although IDK if Chrome and Firefox task managers are directly comparable.
chrismorgan 6y ago
Four years ago, I found Gmail to tend to use 80–200MB in Firefox, mostly in the lower half of that range. Certainly I found the figures in this test utterly unbelievable for this reason; Safari ain’t lighter on memory than Firefox, let alone that much. But also for reference, it’s not like something of Gmail’s complexity has to use that much memory. Fastmail provides equivalent functionality minus chat in a 10–15MB budget, and you can add calendars and contacts (which are separate in Google land) and still keep it to 16–25MB.
lucideer 6y ago
Gmail specifically has massively improved recently for me, but I feel it tends to be more of a spikey graph than a steady trendline over time. Memory usage went through the roof when they first rolled out their current redesign, despite already being far too high before. I assume Gmail will get worse again at some stage. Similarly, Google Docs & Sheets are abysmal currently; not really sure if they were ever significantly better or worse in the past. In terms of webapps, Google's approach has always seemed to be to make things that are powerful, sometimes usable, but with no focus on performance, cross-browser compat, or general industry best practice at all from a frontend engineering perspective. Any engineering quality in Google products has never in my experience lived in client-side code. This is exacerbated by the fact that "code quality" drives in other companies are often sneaked onto managerial priority lists under the guise of SEO requirements, something Google have never needed to meet.

mayli 6y ago

300MB onload, dropped to 240MB after idling for few minutes. Are you sure it's using less than 100MB? in comparison with the post, it takes about 500MB ram, which is weird for such simple webpage. This HN page takes 40MB.

ASalazarMX 6y ago
Oh sorry, I measured it on Firefox. Chrome on Linux started at 160 Mb, and it settled around 150. I've disabled Hangouts, and the right sidebar, so that might account for the differences. Funny how Firefox reports a third of that, although IDK if Chrome and Firefox task managers are directly comparable.

chrismorgan 6y ago

Four years ago, I found Gmail to tend to use 80–200MB in Firefox, mostly in the lower half of that range. Certainly I found the figures in this test utterly unbelievable for this reason; Safari ain’t lighter on memory than Firefox, let alone that much. But also for reference, it’s not like something of Gmail’s complexity has to use that much memory. Fastmail provides equivalent functionality minus chat in a 10–15MB budget, and you can add calendars and contacts (which are separate in Google land) and still keep it to 16–25MB.

lucideer 6y ago

Gmail specifically has massively improved recently for me, but I feel it tends to be more of a spikey graph than a steady trendline over time. Memory usage went through the roof when they first rolled out their current redesign, despite already being far too high before. I assume Gmail will get worse again at some stage. Similarly, Google Docs & Sheets are abysmal currently; not really sure if they were ever significantly better or worse in the past. In terms of webapps, Google's approach has always seemed to be to make things that are powerful, sometimes usable, but with no focus on performance, cross-browser compat, or general industry best practice at all from a frontend engineering perspective. Any engineering quality in Google products has never in my experience lived in client-side code. This is exacerbated by the fact that "code quality" drives in other companies are often sneaked onto managerial priority lists under the guise of SEO requirements, something Google have never needed to meet.