Follow-up bug, once gecko profiling support for raptor-browsertime desktop lands in Bug 1585013: When running cold page-load tests, the browser cycles should be limited to 3 when gecko profiling is enabled. This is already done automatically for warm page-load but we should do the same for cold page-load. This way when running in production we will just get 3 browser cycles and 3 gecko profiles instead of 25. Note that when running locally we still want the --browser-cycles command line arg to override even when --gecko-profile is also enabled, but in production we want to cap browser cycles at 3.
Bug 1603152 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Follow-up bug, once gecko profiling support for raptor-browsertime desktop lands in Bug 1585013: When running cold page-load tests, the browser cycles should be limited to 3 when gecko profiling is enabled. This is already done automatically for warm page-load (reduces page-cycles to 3) but we should do the same for cold page-load and browser-cycles. This way when running in production we will just get 3 browser cycles and 3 gecko profiles instead of 25. Note that when running locally we still want the --browser-cycles command line arg to override even when --gecko-profile is also enabled, but in production we want to cap browser cycles at 3.