|
Topics: |
The Hyperstage configuration file is called infobright.cnf and is located in the ib_data subdirectory within the Hyperstage Data installation directory (for example, C:\ibi\HyperstagePG\ib_data). The configuration file is a text file containing the Hyperstage configuration parameters.
Each parameter is shown on a separate line.
If a parameter is not present in the configuration file or if the configuration file does not exist, the default values are used. Blank lines and comments (lines starting with #) are ignored.
Be sure to customize the following parameters to optimize performance. These tuning parameters are case sensitive and must be typed as shown in the following table.
Note: The values are commented out (preceded by #) in the infobright.cnf file, which causes them to default to the application minimum allowed values of 600 and 320 for ServerMainHeapSize and LoaderMainHeapSize, respectively.
Hyperstage Configuration Parameters
|
Parameter Name |
Description |
|---|---|
|
LicenseFile |
Specifies the path or name of the newly required License file. |
|
LogLevel |
Controls how much information is written to logs. This is similar to the obsolete ControlMessages parameter. |
|
LogRotateSize |
Specifies how large the log file can be before it is rotated and archived. |
|
LogRotateFiles |
Specifies how many log archive files are kept. |
|
KNFolder |
Specifies the folder where Knowledge Grid is stored. |
|
CacheFolder |
Specifies the folder where temporary objects are stored. |
|
ServerMainHeapSize |
Specifies the size (in MB) of the main memory heap. |
|
ThrottleLimit |
Controls how many SELECT queries can run concurrently. |
Important: You must properly configure your memory settings to ensure optimal performance.
The following table shows sample, recommended memory configurations for different systems.
|
System Memory |
Server Main Heap Size |
Loader Main Heap Size |
|---|---|---|
|
64GB |
48000 |
800 |
|
48GB |
32000 |
800 |
|
32GB |
24000 |
800 |
|
16GB |
10000 |
800 |
|
8GB |
4000 |
800 |
|
4GB |
1300 |
400 |
|
2GB |
600 |
320 |
In most cases, the loader does not benefit from larger memory settings. However, increasing the LoaderMainHeapSize can help when:
or
You can use more memory at import if you are planning to execute several concurrent load tasks to different data tables. However, disk access may become a bottleneck.
ServerMainHeapSize should be as large as possible, but safely smaller than the amount of physical memory on the machine. If performance decreases because of memory swapping by the operating system, try to set lower heap sizes. We also recommend decreasing the heap size if many users are running queries in parallel.
Note: Hyperstage may use additional memory for heavy loads or queries. Also, other applications on your server will use memory for their processes. It is important that the total of ServerMainHeapSize is less than the total available physical memory. If the system needs to swap memory, performance will be severely impacted.
| WebFOCUS | |
|
Feedback |