Data Engine configuration
Data Engine executes queries against data from the database to provide answers for users & applications.
Before configuring memory limits for Data Engine, review Allocate memory to Data Engine.
You can define the following settings for Data Engine per pod.
| Item | Use this item to |
|---|---|
Maximum cumulative memory | Specify the maximum cumulative memory allocated to the Data Engine process during startup per pod. You can define the memory value in GB, MB, or KB. For example, you can enter into the field one of the following: 13G, 8192M, 4194304K. Alternatively, you can set the value as a percentage of total memory, for example as 50%. The default value is 13G. Note: If Autoconfigure heap & direct is set to On, Data Engine automatically determines the best allocation between heap and direct memory limits based on the specified Maximum cumulative memory. |
Heap limit | Specify the maximum theoretical JVM (Java virtual machine) heap limit per pod. The JVM heap memory does not limit the direct memory available in Data Engine. You can define the memory value in GB, MB, or KB. For example, you can enter into the field one of the following: 13G, 8192M, 4194304K. The default value is 4G. |
Java direct memory | Specify the Java direct memory limit per pod. The Java direct memory is used for query processing. You can define the memory value in GB, MB, or KB. For example, you can enter into the field one of the following: 13G, 8192M, 4194304K. The default value is 8G. If queries are failing on an instance that is running out of memory, you can try increasing the memory that Data Engine is allowed to consume. |
Autoconfigure heap & direct | Define how to configure the heap limit and Java direct memory for Data Engine:
For details, see Allocate memory to Data Engine. |
Comments
0 comments