This document provides some hints for tuning performance of Fredhopper.
 |
It is highly recommended to consult Fredhopper whenever tuning performance or in case you are experiencing problems. In case you change any of the settings mentioned in the table below, always first test on a UAT / Test environment |
Fredhopper Qserver performance tuning
Before you start tuning the performance of the Fredhopper Query Server ensure:
- Your Fredhopper installation fulfills the installation requirements
- Fredhopper does not produce any ERROR or WARN messages in the log/fredhopper.log log file.
- The machine is used exclusively for running Fredhopper
- Your Fredhopper installation is within the Fredhopper Technical Boundaries
- You are properly Sorting Result Sets
If all the above requirements are met you can start checking the following configuration settings:
| Group | Setting | Recommended Value | Effects | File | Comment |
|---|---|---|---|---|---|
| deploy | qserver # of threads | 10 .. 20 per connector | required memory | jboss-server/deploy/jbossweb-tomcat55.sar/server.xml | Set maxThreads for each Connector. |
| deploy | qserver RAM | Take all available but leave room for other apps to avoid swapping. | Prevents full GC | qserver_memory setting | |
| FAS config | maximum lister start index | set to 5000 | Avoid robots to go to end of listers by prev/next. | /com/fredhopper/browser/lister/ItemLister/@max-lister-start-index setting | |
| FAS config | itemstore cache size | 10% of total number of items | Reduces base memory | /com/fredhopper/itemstore/ItemStore/itemstore-cachesize setting | |
| FAS config | itemmanager cache size | 20% of itemstore cache size | Reduces base memory | /com/fredhopper/product/ItemManager/@itemmanager-cachesize setting |
Kommentare
0 Kommentare
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.