BatchUpdateChunkSize: BatchUpdateChunkSize can impact performance by reducing the number of round trips required to complete an insert, update, or delete operation. For example, at the default setting of 200 rows, a 10,000 row insert operation would require 50 round trips. Setting BatchUpdateChunkSize to 500 rows would reduce the number of round trips to 20.

CreateMap: CreateMap determines whether the driver creates the internal files required for a relational map of the native data when establishing a connection. When the driver creates these internal files, an initial connection can take a few minutes, depending on network speeds and the amount of metadata the driver must retrieve from the service. For example, when CreateMap is set to OnChange (the default) and changes have been made to the Dynamics 365 back-end schema, the connection may be delayed because the driver runs a discovery on the Dynamics 365 schema and overwrites the internal files used to create a relational map of the data.

FetchSize: FetchSize can be used to adjust the trade-off between throughput and response time. In general, setting larger values for FetchSize will improve throughput, but can reduce response time. You should set FetchSize to suit your environment. Smaller fetch sizes can improve the initial response time of the query. Larger fetch sizes improve overall fetch times at the cost of additional memory.

InsensitiveResultSetBufferSize: To improve performance when using scroll-insensitive result sets, the driver can cache the result set data in memory instead of writing it to disk. By default, the driver caches 2 MB of insensitive result set data in memory and writes any remaining result set data to disk. Performance can be improved by increasing the amount of memory used by the driver before writing data to disk or by forcing the driver to never write insensitive result set data to disk. The maximum cache size setting is 2 GB.

ShowNameColumns: ShowNameColumns exposes an additional name column for Choice, Yes/No, and Lookup field types in Dynamics CRM apps. Enabling this property may impact runtime performance for two reasons. First, additional server processing is required to resolve field labels. Second, response payload sizes increase because both original and name column data are returned.