Meetings: Add notes from 2016-06-01 meeting.

[joshgav]

Please check for technical and editorial accuracy. Thanks!

Closes #49.

/cc @mhdawson @matthewloring @ofrobots @paulirish @pavelfeldman @caseq @jasonLaster @pmuellr @fmeawad @auchenberg

[mhdawson]

Subject to the suggested changes already made ltgm.

[joshgav]

Updated, PTAL.

[pavelfeldman]

it sounded like explicit trace points are the current solution, vision and WIP is to move to sampling

Not exactly. We should use trace points (TRACE_EVENT) for C++ instrumentation of the engine and modules, but we should run sampler at all times for complete JS coverage (both engine and user land).

We can already collect JS samples in the tracing format so that the whole profile was a single payload, but we are not satisfied with the memory footprint it generates. So we are working on a revised format that would scale. In the meanwhile, we simply start both Tracing and JS profiler (sampler) and merge reports on the client side.

[joshgav]

Added Pavel's comment into the notes directly (used a bullet to indent it).

Good to merge?