Issue metadata
Sign in to add a comment
|
[Component Request] OS>Performance |
||||||||||||||||||||||
Issue description1] Component Name: Performance 2] Parent Component (e.g. Blink, UI>Browser, etc...): OS 3] Description of Component: ChromeOS Performance 4] Admin/ Owner: bccheng@ 5] Please specify what triage practices will be followed for the component (i.e. what team will do it and how frequently). group cros-perf-detectives@ will check weekly
,
Mar 28 2017
Here's a really brief DD for what we're planning to do with the Speed program wrt. triage: https://docs.google.com/document/d/19dpu0Si0Tg7JOvVuPOoFyrdfwSmrmsV4IHNhdQ11IMo/edit In short: The Speed component is going to be used by teams dedicated to Speed, e.g. Speed Operations (sullivan@, et. al.) and Speed Metrics (tdresser@, et. al.). The Performance- labels will be used for tracking specific categories of regressions we find. We hadn't considered ChromeOS as we're only planning to cover Win, OSX, Android and Linux. I'd like to discuss if bccheng@ believes there's crossover or redundancies. Otherwise, OS seems like the right place as everything under that is ChromeOS, right?
,
Mar 30 2017
Thanks for the additional info. For "Chrome on ChromeOS" performance issues I think it is already covered now as we can select "Chrome" in the "OS" section in the UI. We'd like to add the Performance component under OS to cover ChromeOS platform performance issues, including compiler tuning, swap size customization, benchmark/workload development, etc. Since OS is only used for ChromeOS, adding the Performance sub-component there seems the most appropriate place.
,
Apr 7 2017
Friendly ping - can we get "performance" added under OS for platform performance issues?
,
Apr 10 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by laforge@google.com
, Mar 28 2017