anchor.diff:  <2> Each profile contains a section which holds details about the query execution
   <3> Each profile has a single time representing the cumulative rewrite time
   <4> Each profile also contains a section about the Lucene Collectors which run the search
  +<5> Each profile contains a section which holds the details about the aggregation execution
   
   Because a search request may be executed against one or more shards in an index, and a search may cover
   one or more indices, the top level element in the profile response is an array of `shard` objects.
  
positive.code: showing the intermediate results, the total rewrite time is simply displayed as a value (in nanoseconds).  This
  value is cumulative and contains the total time for all queries being rewritten.
  
  === A more complex example
  
  To demonstrate a slightly more complex query and the associated results, we can profile the following query:
  
  
negative.code: to execute the post_filter (and in turn wraps the normal scoring SimpleCollector), a BucketCollector to run
  all scoped aggregations.  In the MatchAll search, there is a single GlobalAggregator to run the global aggregation.
  
  ==== Understanding MultiTermQuery output
  
  A special note needs to be made about the `MultiTermQuery` class of queries.  This includes wildcards, regex and fuzzy
  queries.  These queries emit very verbose responses, and are not overly structured.
  