@nikomatsakis keeps asking if we intend to make the full profiling data available on perf.rlo via a clickable link to https://profiler.firefox.com.
And he keeps asking with good reason, I'd say
In order to give an answer, we'd need to find out:
I think points 1 and 3 are the ones posing the highest risks to feasibility.
I would not worry about data quantity, for this sort of thing I'd start uploading to S3 -- that would not be particularly hard.
(we'd clean results every 90 days or w/e, but that seems fine)
processing time is a concern
(but I imagine we might be able to sidestep it if we do it in parallel -- we do have parts of the build that are not being profiled, so other stuff running at the same time -- I also imagine the overhead would not be that high)
It would be good get some rough estimates on both data sizes and processing time
I think crox is pretty quick, actually
but that step could also be done on another machine if we uploaded the raw data to it
sure -- though that upload itself might be slow :)