...
Setting | Description | ||||||
|---|---|---|---|---|---|---|---|
Storage Host | You can only select Automatic. When you select Automatic, the EC used by the running workflow is automatically applied. Alternatively, if the Aggregation Session Inspector is used, a storage host is selected automatically. For further information, see Aggregation Session Inspector(4.3).
| ||||||
Directory | Enter the directory on the Storage Host where you want the aggregation data to be stored.
| ||||||
If Partial File Count | In this field is greyed out with a stated directory, it means that the directory path has been hard-coded using the
| ||||||
Partial File Count | In this field, you can enter the maximum number of partial files that you want to store. Consider the following: Startup: All the files are read at startup. It takes longer if there are many partial files. Transaction commitment: Many small files (large Partial File Count) increase performance when the transactions are committed. In a batch workflow, use this variable to tune performance.
| ||||||
Max Cached Sessions | Enter the maximum number of sessions to keep in the memory cache. This is a performance-, you can enter the maximum number of partial files that you want to store. Consider the following: Startup: All the files are read at startup. It takes longer if there are many partial files. Transaction commitment: Many small files (large Partial File Count) increase performance when the transactions are committed. In a batch workflow, use this variable to tune performance.
| ||||||
Max Cached Sessions | Enter the maximum number of sessions to keep in the memory cache. This is a performance-tuning parameter that determines the memory usage of the Aggregation agent. Set this value to be low enough so that there is still enough space for the cache in memory, but not too low, as this will cause performance to deteriorate, see Performance Tuning with File Storage(4.3) for more information. | ||||||
Enable Separate Storage Per Workflow | This option enables each workflow to have a separate session storage. Multiple workflows are allowed to run simultaneously using the same Aggregation profile. If this checkbox is selected, a workflow will never see a session from another workflow. |
...
The Advanced tab is available when you have selected Couchbase Storage, Elasticsearch Storage, Redis Storage or SQL Storage in the Session tab. It contains properties that can be used for performance tuning. For information about performance tuning, see Aggregation Performance Tuning(4.3).
These fields supports parameterization using ${} syntax, see Profiles(4.3) for more information on how parameterization works.
Couchbase Storage
...
You can also set the properties listed in the Advanced tab as Execution properties. This will override the values that are set in the profile, including default values.
...
Example - Overriding the Advanced properties
...
| language | text |
|---|
...
. For information about performance tuning, see Aggregation Performance Tuning(4.3).
These fields supports parameterization using ${} syntax, see Profiles(4.3) for more information on how parameterization works.
Couchbase Storage
...
You can also set the properties listed in the Advanced tab as properties in the ECDs, which will override the values that are set in the profile, including default values.
Note!
See the Note at the end of this page for more information when using pessimistic or optimistic locking mechanisms for Couchbase aggregation storage.
...