...
The aggregation session data is fetched using an N1QL query.
...
Note!
N1QL queries are used by default. If you want to use views instead, set the property mz.cb.use.n1ql
to false
in ECs.
The data returned by the query is split into chunks of a configurable size. The size of each partial set of data can be configured by setting the property view.iteratorpageSize
in the Advanced tab of the assigned Couchbase profile. Setting a higher value than the default 1000 may increase throughput performance but it depends on the available RAM of the Execution Context host.
...
Excerpt | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Session Storage FormatThe aggregation sessions are stored in JSON format. However, some of the data within the JSON strings can be stored in binary format instead of plain text (default). You can change the stored format by setting the property
The Aggregation agent can read stored session data in both formats, regardless of the selected value. In order to To obtain the best possible performance in the Aggregation agent, you should use the binary format.
|
Replication and Persistence
You can use the properties mz.cb.awaitPersistenceTo
and mz.cb.awaitReplicationTo
in the Advanced tab of the selected Couchbase profile to minimize the risk of data loss. However, setting a higher value than the default 0 will reduce the throughput performance.
Automated Index Updates
...
Note!
This section only applies if you are using ‘view’ instead of ‘queries’.
In order to obtain the best possible performance in the Aggregation agent, you should disable automatic index updates in Couchbase.
...