anchor.diff:  `search_multi`::
   
       A collector that wraps several other collectors.  This is seen when combinations of search, aggregations,
  -    global aggs and post_filters are combined in a single search.
  +    global aggs, and post_filters are combined in a single search.
   
   `search_timeout`::
   
  
positive.code: ==== Performance Notes
  
  Like any profiler, the Profile API introduces a non-negligible overhead to search execution.  The act of instrumenting
  low-level method calls such as `collect`, `advance` and `next_doc` can be fairly expensive, since these methods are called
  in tight loops.  Therefore, profiling should not be enabled in production settings by default, and should not
  be compared against non-profiled query times.  Profiling is just a diagnostic tool.
  
  
negative.code: // TEST[s/_search/_search\?filter_path=profile.shards.aggregations/]
  // TEST[continued]
  
  This yields the following aggregation profile output:
  
  [source,js]
  --------------------------------------------------
  