gradle says this at the very top of its output when you invoke it:

> gr help
Starting a Gradle Daemon (subsequent builds will be faster)
Parallel execution is an incubating feature.

See the profiling report at: file:///redacted/path/to/profile-2018-08-31-17-05-31.html
A fine-grained performance profile is available: use the --scan option.
Parallel execution with configuration on demand is an incubating feature.

(1) there's a pause of a few seconds after the first line, but it explicitly says because it's making a new daemon, so the user isn't left hanging. i don't think we make it clear when the daemon is restarting -- usually it's clear because things will be slower, but visibility into that might make it less annoying than a mysterious feeling of "pants is sometimes much slower when i start it up" (which could lead to further mysterious feelings such as "python startup cost is absurd") (2) it seems a little much to put a link to a profiling report on every single run, but one thing we could do that would be similar is put a link to the current build that resolves to the correct page if the user has

./pants server

running elsewhere, and then people don't have to remember/search for the timings, and can look at them and become more familiar if they're curious (and the result of

./pants server

is much more useful than a profiling report for 99% of users i would think) (3) "parallel execution is an incubating feature" says nothing at all about what the feature is or when it'll land but it sounds mega hype and people can then search for it who otherwise wouldn't know unless they're diligently reading the release notes i personally find pants's current output really useful, and going to the other end and having too much fluff can be really distracting and cause people's eyes to glaze over. i also think that the first two are things we can potentially replicate in pants (a) without too much effort and (b) without too much resulting clutter.