This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

FWIW, this is not surprising at all. BuildBot streams rendered HTML and renders it. LogDog hosts a non-trivial rendering application including RPCs, authentication, logic, caching, and frameworks (e.g., Polymer). Its base memory requirement will be notably larger for sure.

After logs are rendered, their raw data is made candidate for garbage collection; only the rendered HTML should remain. Consequently, its per-log memory usage should scale similarly with BuildBot.

Both applications have a base memory cost and a per-log cost. The per-log costs should be similar, since they both render logs similarly. The base cost for LogDog is expected to be much higher, and this is WAI.

450MB memory for 3MB text is a huge overhead, whether it is per log or the base one. LogDog webpage isn't the only webpage opened at a time and until every machine ships with TB of RAM, I think 450MB ram requirement is not acceptable.

However, good news is that today, the same page is just 100MB, which is better than buildbot was. So, I think this has actually greatly improved in last year.