| View previous topic :: View next topic |
| Author |
Message |
Immrec
Joined: 27 Jul 2012
Posts: 30
Location: Australia
|
 Posted: Thu May 09, 2013 8:41 am Post subject: Slow responce from Server |
 |
|
Since the upgrade to Version 6, we have noticed that when a workstation opens Pagegate, it takes several minutes for the GUI to open, then the response to enter messages and select recipients is very slow. It doesn't happen every time we open PG, but when it does happen it's when we need it most to dispatch a Rescue squad or Rural Fire Brigade.
PG is running on the same server since we installed V5.0, the only change is the upgrade to V6 and the addition of several recipients .
Anyone else experienced this or have any clues that might help narrow the cause?
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Thu May 09, 2013 8:54 am Post subject: |
|
|
| I have an odd test I'd like you to run. On the PageGate Server, open the PG Admin and go to the Logging - Settings section. Once there, uncheck "Use PG Monitor" and click on Apply. Of course, when you do that, the Monitor is going to stop displaying data but after the Monitor isn't in use, try to send out a message or have multiple systems open the PG Client and let us know if that improves the reaction time or not. |
|
| Back to top |
|
Immrec
Joined: 27 Jul 2012
Posts: 30
Location: Australia
|
| Posted: Mon May 13, 2013 7:02 pm Post subject: |
|
|
Thanks,
I've disabled PG Monitoring, will let the system run like this for a few days to see if staff notice any difference and get back to you
|
|
| Back to top |
|
Immrec
Joined: 27 Jul 2012
Posts: 30
Location: Australia
|
| Posted: Wed May 15, 2013 6:24 pm Post subject: |
|
|
Just had a staff member advise that two workstations were very slow to respond, first was still opening PageGate, whilst the second was trying to filter the recipients before sending a message. It can take over 1minute for the GUI to open and then another 20-30sec for a filter request to respond before we can start to type the message.
When we are dealing with Rural Fire Services and Volunteer Rescue units, the delay is too long.
Any additional tests we can run to track down the bottleneck?
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Thu May 16, 2013 6:59 am Post subject: |
|
|
Okay, now that we've determined it isn't a direct TCP packet interruption being caused by the PG Monitor, go ahead and re-enable it. What's really strange is that this behavior from the client is very, very, very odd and not something I can immediately recall happening to many other clients.
If you check the Windows Event Viewer logs, both System and Application, do you see any references to network disruption or connection request timeouts or any sort of warnings/declaratives around the time of the PG Client's connection to the database? There has to be some information about what's happening tucked away somewhere. Also, do you see anything in the PageGate Logs within relative time of the PG Client's connection? Anything mentioned in the scheduler about a file lock missing or rebuilding records or... really, just anything out of the ordinary? |
|
| Back to top |
|
Immrec
Joined: 27 Jul 2012
Posts: 30
Location: Australia
|
| Posted: Thu May 16, 2013 7:45 pm Post subject: |
|
|
I'll sift through the logs for the past week (could take awhile). Also planning on moving PageGate to an XP Pro workstation due to W2k8 driver issues with the Dial-up modems needed for RFS Pagers.
The current server also has IIS installed in prep for Sharepoint, XP will dedicated to PageGate and nothing else so maybe that's the issue, too much happening on the server
|
|
| Back to top |
|
|
