The perf dashboard now tracks byte sizes of (some) key built targets. Scroll to the bottom of the dashboard for the thumbnails.
This is primitive, but provides a place to start adding more sophisticated tracking. Let me know what you'd like to see. Right now, it just tracks the size of various files built by the following builders: - Chromium XP: chrome.dll, chrome.exe, mini_installer.exe, setup.exe - Chromium Linux: chrome, chrome.pak - Mac Perf: Chromium, Chromium.app All of the above are simple byte sizes, with the exception of Chromium.app where it's recording the size of the Chromium.app tree as reported by du -s. The UI is the same as for the perf graphs. Click through on the Linux or Mac graphs and you'll also find graphs for text|data|bass of chrome, or __TXT|__DATA||__OBJ of Chromium (mainly because it was easy to pull that info out of the "size" command). For chrome.dll, chrome.exe and mini_installer.exe, I extracted historical data back to last September from the available continuous snapshots, so there's already some richness to those graphs. The others are all getting populated starting now--that is, as I write this, they're all rather uninteresting blank graphs consisting of a single data point, but should, barring unforeseen problems, start looking more interesting tomorrow. Let me know about problems, questions, suggestions, etc. --SK --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---