In most cases, the loader does not benefit from larger memory settings. However, increasing the LoaderMainHeapSize can help when:

• A table to be loaded has very long text values

  or

• The table has many columns (for example, 1000 columns).

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 in 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.

Important: 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 and LoaderMainHeapSize is less than the total available physical memory. If the system needs to swap memory, performance will be severely impacted.

Note: For information on configuring the Hyperstage adapter and connecting to the database using the Reporting Server, see Using the Adapter for Hyperstage in the Adapter Administration manual.