7 ms·

Wow talk about memory usage expansion: Gmail vintage (0.8 MiB) -> Gmail (158 MiB) -> Inbox (215 MiB) I feel a desire to switch back to the original HTML versi

by icc97 8y ago

Wow talk about memory usage expansion: Gmail vintage (0.8 MiB) -> Gmail (158 MiB) -> Inbox (215 MiB) I feel a desire to switch back to the original HTML version - credit to Google for keeping it going. Here's the handy support page [0] with a link to convert back. Edit: it appears you just need the `/h` appended to the URL [1] [0]: https://support.google.com/mail/answer/15049?hl=en https://support.google.com/mail/answer/15049?hl=en [1]: https://mail.google.com/mail/u/0/h https://mail.google.com/mail/u/0/h

at-fates-hands 8y ago
Wasn't this the initial reason gmail was designed? It had a small footprint and wasn't a performance hog which made it fast, responsive and easy to use? I've read lately Inbox is probably going away after the recent gmail redesign which is incorporating some of Inbox's features.
- deleted 8y ago
  [deleted]
- paulddraper 8y ago
  Gmail's innovation was being a high quality web based email client. It wasn't necessarily "fast" compared to a native client but was optimized enough to run in slow browsers. And with crazy optimizations too. IE6 has bad memory performance for for-in loops. So instead it implement custom key-value structures https://github.com/google/closure-library/blob/master/closure/goog/structs/map.js#L51 https://github.com/google/closure-library/blob/master/closur...
ebikelaw 8y ago
The very lightweight HTML Gmail lacks all of "normal" Gmail's latency-hiding features, which is one reason it uses so little memory. Gmail preloads all of the messages in the thread list so when you click them they are displayed instantly. HTML Gmail doesn't, and when you click a message it fetches the body from the origin. The tradeoff is yours to make. I find the HTML version infuriating when I'm tethered on mobile because every mouse click takes 10 seconds. On the same tether I can leave normal Gmail open all the time and it's fast. Ironically the lightweight Gmail is more usable on a fast, reliable wired connection.
- nine_k 8y ago
  I think that the contents of the emails in a thread is a minor part of 150MiB taken by the full version. I suppose my entire inbox (the not-archived part) is much smaller that that.
  - ebikelaw 8y ago
    Indeed, it's not the data but the code to support it. There's a bazillion features in there designed to avoid the user having to do additional page loads. For example in my Gmail memory profile there's 20+ MB of code to support the real-time chat feature in the sidebar. You can argue about whether there should be a middle ground implementation that has the email preloading but not the real-time chat. Developer and project manager time is unfortunately finite.

by icc97 8y ago

at-fates-hands 8y ago

Wasn't this the initial reason gmail was designed? It had a small footprint and wasn't a performance hog which made it fast, responsive and easy to use? I've read lately Inbox is probably going away after the recent gmail redesign which is incorporating some of Inbox's features.

deleted 8y ago
[deleted]
paulddraper 8y ago
Gmail's innovation was being a high quality web based email client. It wasn't necessarily "fast" compared to a native client but was optimized enough to run in slow browsers. And with crazy optimizations too. IE6 has bad memory performance for for-in loops. So instead it implement custom key-value structures https://github.com/google/closure-library/blob/master/closure/goog/structs/map.js#L51 https://github.com/google/closure-library/blob/master/closur...

ebikelaw 8y ago

The very lightweight HTML Gmail lacks all of "normal" Gmail's latency-hiding features, which is one reason it uses so little memory. Gmail preloads all of the messages in the thread list so when you click them they are displayed instantly. HTML Gmail doesn't, and when you click a message it fetches the body from the origin. The tradeoff is yours to make. I find the HTML version infuriating when I'm tethered on mobile because every mouse click takes 10 seconds. On the same tether I can leave normal Gmail open all the time and it's fast. Ironically the lightweight Gmail is more usable on a fast, reliable wired connection.

nine_k 8y ago
I think that the contents of the emails in a thread is a minor part of 150MiB taken by the full version. I suppose my entire inbox (the not-archived part) is much smaller that that.
- ebikelaw 8y ago
  Indeed, it's not the data but the code to support it. There's a bazillion features in there designed to avoid the user having to do additional page loads. For example in my Gmail memory profile there's 20+ MB of code to support the real-time chat feature in the sidebar. You can argue about whether there should be a middle ground implementation that has the email preloading but not the real-time chat. Developer and project manager time is unfortunately finite.