Very nice work, uhm can we create a navigation bar to the perf page :) It seems there are too many.
On Fri, Apr 17, 2009 at 11:44 AM, Jeremy Moskovich <[email protected]>wrote: > > +1 It's great that we can track this info now, thanks for doing this! > > Nicolas: Could you possibly add the contents of your email to the wiki? > > sgk: How about adding links from the top of the page to the size graphs? > Since they're way down at the bottom of the page it's easy to miss them. It > would also be cool if the wiki had some explanation of what each graph is > measuring? > > Best regards, > Jeremy > > > On Fri, Apr 17, 2009 at 7:53 AM, Nicolas Sylvain <[email protected]>wrote: > >> Thanks! This is awesome. >> Since "Where are the perf graphs?" is one the most asked questions, I will >> answer it even before someone asks: >> >> Go to the waterfall (http://build.chromium.org), click on the perf link >> in the top left corner. >> >> To find the size graphs, scroll down to the bottom of the page. Click on >> the graph name to see it bigger. >> >> Quick link to chrome.dll over the last 6000 revs : >> >> http://build.chromium.org/buildbot/perf/xp-release/sizes/report.html?header=chrome.dll&graph=chrome.dll&history=1200 >> >> Quick link to chrome.exe over the last 6000 revs : >> >> http://build.chromium.org/buildbot/perf/xp-release/sizes/report.html?header=chrome.exe&graph=chrome.exe&history=1200 >> >> Nicolas >> >> On Fri, Apr 17, 2009 at 12:03 AM, Steven Knight <[email protected]> wrote: >> >>> 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: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
