Looking at the docs:
Along with aggregate pushdown optimization, an application can further enhance the aggregate query performance by computing aggregation in parallel for each partition in the index service. This can be achieved by specifying the parameter
max_parallelismwhen issuing a query. The value for
max_parallelismshould match the number of partitions of the index Note than when this is enabled, the index service uses more CPU and memory since the query traffic is increased according to the value set in the parameter
Does "when this is enabled […] since the query traffic is increased according to the value set in the parameter
max_parallelism " imply that without that setting, the query engine will query the index partitions sequentially?
Meaning that if I have n partitions (on say Meta().id) on n index nodes, the query engine will get results from [1,n] one after the other?