Solution : https://service.sap.com/sap/support/notes/1269480 (SAP Service marketplace login required)
Key words :
java application response time measurement, choosing good heap settings, kb runtime version definition, writing logs costs performance, variant table size limited, mentioned kernel patch level, knowledge base runtime versions, java virtual machine, kb runtime versions, crm mobile sales
Related Notes :
| 1248104 | Information about size and content of KB runtime versions |
| 1241435 | KB search for subitems is superfluous |
| 1239594 | VMC logging standard is reduced to ERROR |
| 1227157 | buffered access to variant tables |
| 1224955 | VMC performance improvement in MSA scenario |
| 1223137 | Dependencies being executed twice |
| 1170313 | Zero administration memory management in VMC |
| 1139442 | Prevent unnecessary update in CrmUpdateConfiguration |
| 1124499 | Caching of variant tables, direct database calls |
| 1083358 | VMC: Empfehlungen für Parameter-Einstellungen |
| 1081650 | Modeling tips for the use of the IPC |
| 1020539 | Memory management in the VM container |
| 1005457 | Parameter setting for Java Virtual Machine in VM Container |
| 997111 | JARM instrumentation of the configuration |
| 992115 | Bad performance of KB load function |
| 981556 | Performance improvement: get knowledgebase as mapping |
| 980914 | Performance Optimization Of Interactive Configuration |
| 966929 | Performance: Lazy load of instances |
| 966013 | Variant table size limited to 100.000 rows |
| 930440 | Potential pitfalls in KB runtime version definition |
| 923761 | Procedural relationships are analyzed too often |
| 888255 | Archiving knowledge base runtime versions does not work |