Clarified usage of --optimize flag

daniel-percona · daniel-percona · commit de8449805dba · 2025-04-29T10:45:56.000-04:00
diff --git a/README.md b/README.md
@@ -259,5 +259,5 @@ You have a wide range of options available, and the parameters are neither exclu
 
 16. Optimized Workload
   
-  - This setting is disabled by default, allowing the workload to run all queries, including both optimized and ineffective queries. To run a more optimized workload, provide the `--optimized` argument when executing the workload. This ensures that queries use the flight ID for retrieval, rather than a range of flight IDs and other less optimal queries. In a sharded cluster, querying by a range of flight IDs can be inefficient, potentially leading to scatter/gather queries. Since the flight ID is indexed and serves as the shard key in sharded clusters, using it for queries improves performance and efficiency.
+  - This setting is disabled by default, allowing the workload to run all queries, including both optimized and ineffective queries. To run a more optimized workload, provide the `--optimized` argument when executing the workload. This ensures that queries use the flight ID for retrieval, rather than a range of flight IDs and other less optimal queries Since the flight ID is indexed and serves as the shard key in sharded clusters, using it for queries improves performance and efficiency. In addition, providing this flag will enable find workloads to only run aggregate queries, as these are faster since they do not require sending records back from DB to client. 
 

Original file line number	Diff line number	Diff line change
`@@ -259,5 +259,5 @@ You have a wide range of options available, and the parameters are neither exclu`
`259`	`259`
`260`	`260`	`16. Optimized Workload`
`261`	`261`
`262`		- - This setting is disabled by default, allowing the workload to run all queries, including both optimized and ineffective queries. To run a more optimized workload, provide the `--optimized` argument when executing the workload. This ensures that queries use the flight ID for retrieval, rather than a range of flight IDs and other less optimal queries. In a sharded cluster, querying by a range of flight IDs can be inefficient, potentially leading to scatter/gather queries. Since the flight ID is indexed and serves as the shard key in sharded clusters, using it for queries improves performance and efficiency.
	`262`	+ - This setting is disabled by default, allowing the workload to run all queries, including both optimized and ineffective queries. To run a more optimized workload, provide the `--optimized` argument when executing the workload. This ensures that queries use the flight ID for retrieval, rather than a range of flight IDs and other less optimal queries Since the flight ID is indexed and serves as the shard key in sharded clusters, using it for queries improves performance and efficiency. In addition, providing this flag will enable find workloads to only run aggregate queries, as these are faster since they do not require sending records back from DB to client.
`263`	`263`