anchor.diff:  [[docs-delete-by-query-automatic-slice]]
   ==== Automatic slicing
   
  -You can also let delete-by-query automatically parallelize using
  -<<sliced-scroll>> to slice on `_uid`. Use `slices` to specify the number of
  +You can also let delete by query automatically parallelize using
  +<<sliced-scroll, sliced scroll>> to slice on `_uid`. Use `slices` to specify the number of
   slices to use:
   
   [source,js]
  
positive.code: automatic slicing, use these guidelines.
  
  Query performance is most efficient when the number of `slices` is equal to the
  number of shards in the index. If that number is large, (for example,
  500) choose a lower number as too many `slices` will hurt performance. Setting
  `slices` higher than the number of shards generally does not improve efficiency
  and adds overhead.
  
  
negative.code: wait_time = target_time - write_time = 2 seconds - .5 seconds = 1.5 seconds
  --------------------------------------------------
  
  Since the batch is issued as a single `_bulk` request, large batch sizes will
  cause Elasticsearch to create many requests and then wait for a while before
  starting the next set. This is "bursty" instead of "smooth". The default is `-1`.
  
  