Difference between revisions of "Performance Tweaks"
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
<ol> | <ol> | ||
<li>[[Database_Indexing|Index the PTS database]].</li> | <li>[[Database_Indexing|Index the PTS database]].</li> | ||
<li>Turn off [[Label_Printer_Installation|bi-directional support]].</li> | <li>Turn off [[Label_Printer_Installation|bi-directional support]]. <i>(Please do not underestimate the performance impact of this setting even if you have never heard of it before)</i></li> | ||
<li>Use a resource monitor or the SQL performance dashboard to identify the application at fault and then contact the manufacturer.</li> | <li>Use a resource monitor or the SQL performance dashboard to identify the application at fault and then contact the manufacturer.</li> | ||
<li>Use SQL performance dashboard to identify the expensive query and have IT or the manufacturer optimise it and/or reduce its frequency.</li> | <li>Use SQL performance dashboard to identify the expensive query and have IT or the manufacturer optimise it and/or reduce its frequency. <i>(This issue seems to be becoming more common, please test your queries for performance at scale before rollout)</i></li> | ||
<li>Consider upgrading your server hardware to the [[High_Level_Design_Document|recommended PTS 5 specification]].</li> | <li>Consider upgrading your server hardware to the [[High_Level_Design_Document|recommended PTS 5 specification]].</li> | ||
</ol> | </ol> | ||
Revision as of 13:18, 19 July 2022
Like all software, PTS 5 is not immune to occasional temporary performance issues.
Symptoms
Various functions of the PTS application take an unsatisfactory amount of time to load or to process.
Common causes
- The database has grown large and the data has become fragmented.
- Printer settings are not optimal.
- Other software on a shared server is hogging resources.
- An unoptimised or expensive third party query is hitting the PTS database.
- The server/s only meet the bare minimum hardware requirements.
Solutions
- Index the PTS database.
- Turn off bi-directional support. (Please do not underestimate the performance impact of this setting even if you have never heard of it before)
- Use a resource monitor or the SQL performance dashboard to identify the application at fault and then contact the manufacturer.
- Use SQL performance dashboard to identify the expensive query and have IT or the manufacturer optimise it and/or reduce its frequency. (This issue seems to be becoming more common, please test your queries for performance at scale before rollout)
- Consider upgrading your server hardware to the recommended PTS 5 specification.