you're right, the claculation of proximity takes "a lot" of cpu time so user feels like it's monitor is frozen.
In october, we've increase our limit from 10 to 20 and now we're thinking moving backward to 5 because it's very very slow.
It was not that slow in october because at that time we did not changed other parameters. Since then, we've change 2 other parameters into wsgpositionandstatus.dll.config to make sure that mapping information position represent real filed position (we units are moving and crossing streets).
To be as real time as it can be, we've changed reportintervalms from 2000 to 160000 (that has probably no effect on our priximity monitor)
We've alos changed minimumreportingdistancemeters from 100 to 6... Which means that when a unit is moving, we've and update after each 6 meters. This is causing refresh of our proximity monitor and users, when they are into patrol dashboard, feel like computer is frozen...
Any idea on how we should configure our paramters to make sure mapping is near rela time and patroldashbord works correctly?
Report intervals faster than every 2 seconds tend to cause performance issues in MPS.
GPS devices tend to be only accurate to about 10 meters, so a setting of 6 meters could have an impact. Even with a higher setting, the unit position should settle to the final position, i.e. it will "catch up" when the report interval passes and won't be left 100 meters away...
What version of MPS are you running? There was at least one performance fix in the last couple years to the Patrol Dashboard that was not proximity related (if I recall correctly).
As for how you should adjust the settings, it depends on a number of factors like what hardware is in the clients and how many units are being sent to MPS.
Have you restricted the number of sentences coming in from the GPS? If its NMEA, you really only need the RMC sentence. It's best to restrict it at the GPS device itself, but if that's not feasible then set the acceptedSentenceTypes setting.
I see. Wasn't sure if the 160000 was what you really meant, but it is. So it may take that long to "catch up" that last reporting distance, or fraction thereof. I.e. you may appear close to your destination after arrival, but off by 0 - 6 meters, then get a final adjustment after the 160 seconds.
If you get jitter with the 6 meter setting you might bump it up a little (e.g. 8 - 12 meters), some GPS devices are more stable than others.
Tweaking it by experimentation with your equipment is the best approach, as you are doing. Bear in mind it won't ever get super fast. Good luck.