The connection properties described in this topic have direct impact on driver performance.
BulkActivityPageSize. The BulkActivityPageSize connection property specifies the maximum number of rows to be fetched from Activity_XXX tables in a single request. Generally, higher page sizes return results more quickly. However, Oracle Eloqua imposes a 32 MB limit on response package size. If queries return large records, too many records within a single page will exceed that limit, causing the query to fail. In addition, all of the objects returned within a page must be materialized as the page is retrieved, so sufficient Java heap space is necessary with large page sizes containing many small columns.
BulkPageSize. The BulkPageSize connection property specifies the maximum number of records to be fetched in a single request. Generally, higher page sizes return results more quickly. However, Oracle Eloqua imposes a 32 MB limit on response package size. If queries return large records, too many records within a single page will exceed that limit, causing the query to fail. In addition, all of the objects returned within a page must be materialized as the page is retrieved, so sufficient Java heap space is necessary with large page sizes containing many small columns.
BulkTopThreshold. The BulkTopThreshold connection property can be used to determine the point at which bulk operations can be used to execute qualifying Select queries. See Bulk operations for more information on qualifying Select queries.
WSFetchSize. The WSFetchSize connection property allows you to specify the maximum number of rows allowed for a fetch on each call to the web service. The default value of 1000 rows typically provides the maximum throughput. However, for interactive applications, you can reduce response time by setting WSFetchSize at a lower value.
