Performance issues - Revision history

Jennyurey at 00:24, 2 March 2021

2021-03-02T00:24:26Z

Admin: /* Determining if PARS is Running Slowly */

2018-10-25T09:25:57Z

Determining if PARS is Running Slowly

Admin: /* Identifying the Issue */

2018-10-25T09:25:14Z

Identifying the Issue

Admin: /* Software Optimisations */

2018-10-25T09:23:28Z

Software Optimisations

Admin: /* Automation */

2018-10-25T09:22:34Z

Automation

Admin: /* Software Optimisations */

2018-10-25T09:22:00Z

Software Optimisations

Admin: /* Potential Resolutions */

2018-10-25T09:20:39Z

Potential Resolutions

Admin: /* SQL Server */

2018-10-25T09:20:08Z

SQL Server

Admin: /* SQL */

2018-10-25T09:19:46Z

SQL

Admin: /* SIMS Tweaks */

2018-10-25T09:13:20Z

SIMS Tweaks

← Older revision		Revision as of 00:24, 2 March 2021
Line 12:		Line 12:

	Hold down CTRL and SHIFT when opening a register from the main PARS Connect diary page. Any register will do. <br> <br>		Hold down CTRL and SHIFT when opening a register from the main PARS Connect diary page. Any register will do. <br> <br>
		+	Seating plan trace can be viewed when clicking 'seating plan' and CTRL, SHIFT, ALT from a register

	This will open a Trace Window when loading the register. The Trace Window records the exact times taken by various functions required to open a register. On a decent system a register should take less than 5 seconds to open. On a well-configured system a register will take less than 2 seconds to open. <br> <br>		This will open a Trace Window when loading the register. The Trace Window records the exact times taken by various functions required to open a register. On a decent system a register should take less than 5 seconds to open. On a well-configured system a register will take less than 2 seconds to open. <br> <br>

@@ Line 23: / Line 23: @@
 Exper Method 2 should take less than 3 seconds; if it does not, follow the instructions below. If Exper Method 2 take less than 3 seconds then check the other times in the Trace Window. Several times highlighted in orange or red indicates an issue with the SQL server. <br> <br>
-If the register is taking more than 5 seconds to load, Exper Method 2 is taking less than 3 seconds and one or two times in the Trace Window are highlighted in orange or red, post a ticket on the [[help|helpdesk]] with a screenshot of the Trace Window. <br>
+If the register is taking more than 5 seconds to load, Exper Method 2 is taking less than 3 seconds and one or two times in the Trace Window are highlighted in orange or red, post a ticket on the '''[[help|helpdesk]]''' with a screenshot of the Trace Window. <br>
 '''In any other case, the root cause of performance issues in PARS lies with either your IIS server or your SQL server (or both).''' <br> <br>

@@ Line 26: / Line 26: @@
 '''In any other case, the root cause of performance issues in PARS lies with either your IIS server or your SQL server (or both).''' <br> <br>
-=Identifying the Issue=
+=Server Issues=
-In general terms any performance issues will be lie with either the IIS server (due to overuse) or with the SQL server. Use this page to decide whether it is the IIS server or SQL server causing the issue: <br>
+In general terms any performance issues will be lie with either the IIS server (due to overuse) or with the SQL server. Use this section to decide whether it is the IIS server or SQL server causing the issue: <br>
-'''[[PARS main menu]]''' > '''[[System management]]''' > '''System''' > '''Performance monitor''' <br> <br>
+'''PARS main menu''' > '''[[System management]]''' > '''System''' > '''Performance monitor''' <br> <br>
-==IIS==
+==IIS Server==
 The easiest to rule out (and to fix) is the IIS server. <br> <br>
@@ Line 43: / Line 43: @@
 Running the IIS server as a Virtual Machine can cause additional problems; Power Saving features can be left on and there may be settings on the Host to limit CPU performance to a percentage of the host's capability (nominally to maintain CPU cycles for other VM guests) that will have the effect of crippling the IIS server's performance. <br> <br>
-==SQL==
+==SQL Server==
-If the IIS server is running well turn your attention to the SQL server. This will have the same potential pitfalls and more when running as a virtualised machine and sharing the host with the IIS server. <br> <br>
+If the IIS server is running well turn your attention to the SQL server. This will have the same potential pitfalls as the IIS server, and more, when running as a virtualised machine and sharing the host with the IIS server. <br> <br>
 A very realistic test of the SQL server can be performed using the following: <br>

@@ Line 69: / Line 69: @@
 '''[[PARS main menu]]''' > '''[[System management]]''' > '''System''' > '''[[Automation]]''' > '''Status''' <br> <br>
-If automation is running but not building data caches, run a [[service pack|PARS Service Pack]]. <br> <br>
+If automation is running but not building data caches, run a '''[[service pack|PARS Service Pack]]'''. <br> <br>
 ===Blockers===

@@ Line 64: / Line 64: @@
 Automation should also build data caches so that end users do not have to. To test that automation is building the caches go to: <br>
-'''[[PARS main menu]]''' > '''[[System management]]''' > '''System''' > '''[[Cache viewer]]''' <br>
+'''[[PARS main menu]]''' > '''[[System management]]''' > '''System''' > '''[[Cache viewer]]''' <br> <br>
 Each of the PARS caches is listed on this page. Some of the caches should have a yellow background, indicating they were built by the automation module. If none of the caches have yellow backgrounds, check that automation is running by going to: <br>
 '''[[PARS main menu]]''' > '''[[System management]]''' > '''System''' > '''[[Automation]]''' > '''Status''' <br> <br>

@@ Line 54: / Line 54: @@
 If your Table Speed Test times exceed those stated above, use the instructions on the '''[[SQL server performance]]''' page to diagnose and resolve issues on the SQL server. <br> <br>
-=Potential Resolutions=
+=Software Optimisations=
 ===Automation===

@@ Line 87: / Line 87: @@
 Archiving attendance data. Capita recommend that you archive your attendance data ever year. If this has not been done for many years, it can cause performance issues. Contact your SIMS team for advice on this. <br> <br>
 [[Category:System management]]
 [[Category:Technical]]
 [[Category:Troubleshooting]]

@@ Line 45: / Line 45: @@
 ==SQL==
-If the IIS server is running well turn your attention the the SQL server. This will have the same potential pitfalls and more when running as a virtualised machine and sharing the host with the IIS server. <br> <br>
+If the IIS server is running well turn your attention to the SQL server. This will have the same potential pitfalls and more when running as a virtualised machine and sharing the host with the IIS server. <br> <br>
 A very realistic test of the SQL server can be performed using the following: <br>
@@ Line 62: / Line 51: @@
 This is a stress test that attempts to write a number of records to the SIMS and PARS databases, update them and then delete them. This will give a baseline figure as to the performance of the SQL server. You should expect to get around 2 minutes each for the longest PARS tests and 3 minutes each for the longest SIMS tests. If they are much longer than expected, your bottleneck is with the SQL server. <br> <br>
 =Potential Resolutions=

@@ Line 93: / Line 93: @@
 '''[[PARS main menu]]''' > '''[[System management]]''' > '''[[Management reports]]''' > '''Performance''' <br> <br>
-==SIMS Tweaks==
+===SIMS Tweaks===
 Archiving attendance data. Capita recommend that you archive your attendance data ever year. If this has not been done for many years, it can cause performance issues. Contact your SIMS team for advice on this. <br> <br>