Difference between revisions of "Performance Tweaks"
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
<i>(Please do not underestimate the performance impact of this setting even if you have never heard of it before)</i></li> | <i>(Please do not underestimate the performance impact of this setting even if you have never heard of it before)</i></li> | ||
<li>Consider whether your prescription types are set up correctly so that they [[Our prescriptions are not clearing automatically|clear automatically when finished]]. Also see [[User_Views_%26_Homepages#Actions_menu|how to clear lots of prescriptions at once]].<br/> | <li>Consider whether your prescription types are set up correctly so that they [[Our prescriptions are not clearing automatically|clear automatically when finished]]. Also see [[User_Views_%26_Homepages#Actions_menu|how to clear lots of prescriptions at once]].<br/> | ||
<i>We very frequently see PTS configured in such a way that prescription types are marked to require collection, but "collection" is never actually recorded. When a user view is configured to return completed, but uncollected prescriptions, this configuration ultimately results in PTS constantly trying to load a list of ever growing uncollected prescriptions until eventually the server cannot cope with the load.</i></li> | <i>We very frequently see PTS configured in such a way that prescription types are marked to require collection, but "collection" is never actually recorded. When a user view is configured to return completed, but uncollected prescriptions, this configuration ultimately results in PTS constantly trying to load a list of ever growing uncollected prescriptions until eventually the server cannot cope with the load. See [[Our prescriptions are not clearing automatically|this page]] for more.</i></li> | ||
</li> | </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> | ||
Revision as of 13:32, 24 July 2023
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.
- Prescriptions are not being cleared from users homepages and the server cannot cope with the large volume of them.
- 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.
- PTS is trying to reach tmsinsight.com for support contract and software licensing notifications, but your PTS server has no access to the internet.
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) - Consider whether your prescription types are set up correctly so that they clear automatically when finished. Also see how to clear lots of prescriptions at once.
We very frequently see PTS configured in such a way that prescription types are marked to require collection, but "collection" is never actually recorded. When a user view is configured to return completed, but uncollected prescriptions, this configuration ultimately results in PTS constantly trying to load a list of ever growing uncollected prescriptions until eventually the server cannot cope with the load. See this page for more. - 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.
- In Setup > Application Settings, locate the "skip checking if PTS is online" setting (OFFLINE) and set to Yes. This tells PTS not to attempt any remote connections.