Add comment from @pavelfeldman.

Author: joshgav

wg-meetings/2016-06-01.md

@@ -45,6 +45,10 @@ chrome://tracing is intended for platform developers while “Timeline” view i
 
 Currently structural tracing is used, but work is in progress to make sampling tracing more efficient/performant and shift to sampling for most uses. See [this video](https://www.youtube.com/watch?v=nxXkquTPng8) for background on structural vs. sampling tracing.
 
+* @pavelfeldman: 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.
+
 CDP allows configuration of tracing through the Tracing domain:
 https://chromedevtools.github.io/debugger-protocol-viewer/tot/Tracing/