Bugzilla

> I'm thinking about speedometer as an example. 

I found this [speedometer artifact](https://firefoxci.taskcluster-artifacts.net/UnEh5cLDS1WZI9fgA-ysrg/0/public/test_info/perfherder-data.json), which seems to have 160 subtests with 25 cycles per subtest.

> It has a single summary value calculated from X cycles, but we could also make 1 value per cycle and make it a subtest

I'm not sure I got the idea. You mean we should have 25 new subtests named 'speedometer-subtest-cycle-0', ..., 'speedometer-subtest-cycle-24' & each new subtest would aggregate a single replicate for each of the 160 original subtests?

If yes & these subtests have the same name (I think our schema validation considers this legal) **and** we no longer have a summary value, Perfherder would easily ingest 25 geomeans per job & display them in Compare view.

> I'm thinking about speedometer as an example. 

I found this [speedometer artifact](https://firefoxci.taskcluster-artifacts.net/UnEh5cLDS1WZI9fgA-ysrg/0/public/test_info/perfherder-data.json), which seems to have 160 subtests with 25 cycles per subtest. Hopefully it's a good example.

> It has a single summary value calculated from X cycles, but we could also make 1 value per cycle and make it a subtest

I'm not sure I got the idea. You mean we should have 25 new subtests named 'speedometer-subtest-cycle-0', ..., 'speedometer-subtest-cycle-24' & each new subtest would aggregate a single replicate for each of the 160 original subtests?

If yes & these subtests have the same name (I think our schema validation considers this legal) **and** we no longer have a summary value, Perfherder would easily ingest 25 geomeans per job & display them in Compare view.

> I'm thinking about speedometer as an example. 

I found this [speedometer artifact](https://firefoxci.taskcluster-artifacts.net/UnEh5cLDS1WZI9fgA-ysrg/0/public/test_info/perfherder-data.json), which seems to have 160 subtests with 25 cycles per subtest. Hopefully it's a good example.

> It has a single summary value calculated from X cycles, but we could also make 1 value per cycle and make it a subtest

I'm not sure I got the idea. You mean we should have 25 new subtests named 'speedometer-subtest-cycle-0', ..., 'speedometer-subtest-cycle-24' & each new subtest would aggregate a single replicate for each of the 160 original subtests?

If yes & these subtests have the same name within the same `subtests` array value (I think our schema validation considers this legal) **and** we no longer have a summary value, Perfherder would easily ingest 25 geomeans per job & display them in Compare view.