Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| docs:3400_how_to:1100_miscellaneous:1460_optimise [2022/08/25 00:00] – removed - external edit (Unknown date) 127.0.0.1 | docs:3400_how_to:1100_miscellaneous:1460_optimise [2025/06/12 03:59] (current) – Change to AwareIM aware_support3 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | {{tag> | ||
| + | [< | ||
| + | ====== How to optimise application for best performance ====== | ||
| + | |||
| + | Out-of-the-box // | ||
| + | |||
| + | * Performance of business rules | ||
| + | * Performance of queries | ||
| + | * How quickly each request from the user is processed in your system | ||
| + | |||
| + | Below are some recommendations on how to improve performance in each of these areas: | ||
| + | |||
| + | - Check the Log Viewer for the execution of rules that refer to the object (cross reference rules). These may be expensive. Execution of many of them may be unnecessary. Turn them off by going to the Advanced tab of the rule and ticking "Do not check referred" | ||
| + | - Aggregate operations ('' | ||
| + | - Unconditional rules can be expensive (especially if they use aggregate operations). Make them conditional (using '' | ||
| + | - Check for repetitive execution of rules. The rule engine can execute rules repetitively if the next rule triggers a condition that causes the previous rule to fire again. Optimise this carefully. Use rule priorities to make sure that expensive rules are only executed once | ||
| + | - If you find that a particular query does not perform well replace it with a stored procedure (// | ||
| + | - If you need to support many concurrent users make sure that there are no CPU-extensive operations in your application. Or make sure that the CPU-extensive operations are executed at night or by a separate server. | ||
| + | - Add additional servers to scale up your system if necessary (// | ||
| + | |||
| + | |||