SAP Basis Tech Supports

Symptom
You experience a high memory consumption on some or all blades although you have followed the BWA sizing guidelines.
Other terms
BIA, BWA, Accelerator, overload, unloads, slow queries, memory issue
Reason and Prerequisites
Prerequisite:Revision 50 or later
Reason:While processing queries, BWA temporarily needs to store intermediate and final results in main memory. Including the original index data, the amount of main memory might not be enough when there are too many parallel queries.
Solution
You can restrict the number of queries that run in parallel. Further queries will then be queued and are processed one by one as soon as a running query finishes. You configure this in the TREX configuration file “TREXIndexserver.ini”.
1. Start the TREX admin tool (standalone) by entering the following in a command prompt:
cd <TREX_DIR>
./TREXAdmin.sh2. Navigate to the screen area “Landscape: Ini” –> tab “Host”.3. Open the TREX configuration file “TREXIndexserver.ini” for editing by double-clicking on it.4. Insert the line “threads_aggregate_calls = 4″ into section [thread_limit].
If you have more than 4 CPU-cores per blade, adjust the parameter accordingly.5. Choose “Save to All Hosts” to deploy the changes to all hosts of your BWA landscape.6. Restart the TREXIndexservers to activate the changes.