Unsolved

MPS Performance Issues

Comments: 8 - Last Comment by Brett Mitchell on Aug 24, 2016   Comment Filter:
Posted on Aug 18, 2016
 
 

Hi:

We have been running MPS 9.2 MR5 for a year now and just migrated away from the last I/Mobile laptop 3 months ago.

In the past few months we have been having widepsread reports of MPS performance being terrible. It will freeze or slow right down.

We are using LTE modems with what should be plenty of bandwidth. Athough we share the public network and have no guaranteed QOS.

When on the Patrol Dashboard and the vehicle is moving, MPS will hang or performance will be significantly decreased. Often users will be unable to type in the vehicle plate text box (labeled "LIC").

Workflow: They type in the plate, change the province if necessary and press "Enter". In most cases they are not pressing "Traffic Stop". This is different and automatically creates an event and assigns the unit to it. If they are able to type in a license plate and hit enter the Informer results can take 3-5 minutes to come back and the target vehicle is long gone. When the unit is stationary results are returned in seconds.

The Patrol Dashboard Event List:  This list shows the 6 events in closest proximity to the unit as the crow flies. F9 takes you to the patrol Dashboard and refreshes it when you are on it.

Members believe that because the unit is moving and GPS is updating, this list is constantly updating causing the Patrol Dashboard to be unusable.

 

What we have tried:

HSI suggested patching I/MDT and UEDelta which we did. There was no improvement.

We changed the report interval for UEDelta from 10 seconds to 60 seconds. There was no improvement so we changed it back.

We got a javascript change for the PatrolDashboad.htm file that checked for GPS updates every 15 seconds rather than on every update. There was no improvement.

 

Now HSI is suggesting changes to turn off UEDelta and GPS to isolate which may be the problem.

 

Hs anyone else had similar problems, and if so, have you found a solution?

 

Thanks,

 

Brett

Winnipeg Police Service

Point your RSS reader here for a feed of the latest messages in this topic
RE: MPS Performance Issues
Posted on Aug 19, 2016 in response to: Brett Mitchell
 
   
 

How many units do you have on each MTD server in ISM? How often do you delete the .dat file? We're still on MPS 9.2 MR1 with portal, but I have been told that with UEDelta you should only have a max of 250 units defined for each MDTSVR in ISM. The .dat file may or may not be an issue for you, but on the version we are on we have found that whenever units start to have issues with not receiving information or not being able to connect, we need to stop all of the services and the Switchgui and delete the .dat file and that seems to clear up the problems.

RE: MPS Performance Issues
Posted on Aug 22, 2016 in response to: Arthur Meacham
 
   
 

Thanks Arthur.

Restarting the ISM services along with renaming or deleting the ".dat" files is something that we have to do regularly.Unfortunately that does nothing to help with this performance problem.

We have over 4000 units defined but only about 250 laptops and 125 of those online at one time. We have only one MDTSVR defined for this.

Regards,

Brett

RE: MPS Performance Issues
Posted on Aug 22, 2016 in response to: Brett Mitchell
 
   
 

So it doesn't sound like there are too many units (only about 125 active).

The suggestion to "to turn off UEDelta and GPS to isolate which may be the problem", at least on a test machine, is a good one.

Have you looked at CPU usage when the performance is poor? I.e. is the client machine's CPU pegged at 100% (or 50% for a 2 core CPU, etc.)?

How many Events are in the system (at the MPS client)? If there are more than a couple hundred this could be an issue, though I haven't seen the Patrol Dashboard have any significant performance problems. (Can turn on the total counts in the Monitors with setting showTotalItems)

The "Ping Server" command (Menu->Admin->Ping Server...) may help figure out whether the response is slow from the server, and if so whether it is at just MDT (short) or involves MpsAspRptGen (Full).

Have their been any customizations to the Patrol Dashboard that could be contributing to the slowdown?

RE: MPS Performance Issues
Posted on Aug 23, 2016 in response to: Chip Patton
 
   
 

Hi Chip,

We experienced 'freezing' with ~70 events in the uedelta report.  I think our issue is the GPS updates are fed directly to MPS every 2 seconds (upping soon to every second) in order to actively use the map when driving. 

I hope this helps.

Sarah

RE: MPS Performance Issues
Posted on Aug 24, 2016 in response to: Chip Patton
 
   
 

Thanks Chip.

We have our infrastructure people monitoring the speeds and bandwidth. And although we have a problem we are still in the range where MPS should be functioning well.

We have from 100 - 180 events in the queue at any one time.

Thanks for your response,

Brett

RE: MPS Performance Issues
Posted on Aug 23, 2016 in response to: Brett Mitchell
 
   
 

Hi Brett,

We had to change the Patrol dashboard proximity event list to update every 15 seconds instead of at every GPS update.  Let me know if you want to give this 'workaround' a try.

Thanks,

Sarah Byram

Halton Regional Police Consultant

RE: MPS Performance Issues
Posted on Aug 24, 2016 in response to: sbyram
 
   
 

Sarah, could you send me your PatrolDashboard.htm? We tried that and there was no difference. However I think there was a line that should have been commented out that was not.

Thanks,

Brett

bmitchell@winnipeg.ca

RE: MPS Performance Issues
Posted on Aug 24, 2016 in response to: Brett Mitchell
 
   
 

Thanks everyone.

The concensus from the officers was that they do not use the 6 closest events list.
I was resisting disabling that before trying everything else but had no other choice. We disabled the updating for that list and the officers reported a drastic improvement last night.

Sarah, could you send me your PatrolDashboard.htm? We tried that and there was no difference. However I think there was a line that should have been commented out that was not.

Thanks,

Brett


Add a Comment

Please sign in on the right menu to comment.  If you do not have an account, please Join now.