Stream: t-compiler/wg-self-profile

Topic: Making full profiles available on perf.rlo

mw (Oct 25 2019 at 09:48, on Zulip):

@nikomatsakis keeps asking if we intend to make the full profiling data available on perf.rlo via a clickable link to

mw (Oct 25 2019 at 09:49, on Zulip):

And he keeps asking with good reason, I'd say :)

mw (Oct 25 2019 at 09:52, on Zulip):

In order to give an answer, we'd need to find out:

  1. How much data this would produce / how much storage space we'd need
  2. How much processing time it would mean on the benchmarking server (which would have to run crox)
  3. If (or some other online tool) can even handle profiles as large as ours
  4. What makes currently choke on our profiles, which the Chromium tools seem to be able to handle it.
mw (Oct 25 2019 at 09:54, on Zulip):

I think points 1 and 3 are the ones posing the highest risks to feasibility.

simulacrum (Oct 25 2019 at 11:54, on Zulip):

I would not worry about data quantity, for this sort of thing I'd start uploading to S3 -- that would not be particularly hard.

simulacrum (Oct 25 2019 at 11:54, on Zulip):

(we'd clean results every 90 days or w/e, but that seems fine)

simulacrum (Oct 25 2019 at 11:55, on Zulip):

processing time is a concern

simulacrum (Oct 25 2019 at 11:55, on Zulip):

(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)

mw (Oct 25 2019 at 12:24, on Zulip):

It would be good get some rough estimates on both data sizes and processing time

mw (Oct 25 2019 at 12:24, on Zulip):

I think crox is pretty quick, actually

mw (Oct 25 2019 at 12:25, on Zulip):

but that step could also be done on another machine if we uploaded the raw data to it

simulacrum (Oct 25 2019 at 12:37, on Zulip):

sure -- though that upload itself might be slow :)

Last update: Nov 17 2019 at 08:20UTC