AIS Target rendering performance.

[signalk]

AIS Target rendering performance.

[panaaj]

Commit #f373a8b addresses this issue.

[tkurki]

I have absolutely no idea how Angular works, but based on the cursory peek into the code it looks to me that you are looping over all the accumulated data for each incoming delta, instead of just updating the part that is actually updated. This not just for ais targets, but all data.

Do you have logic to remove stale ais targets? Deltas just stop for them when they go out of range.

[panaaj]

It is best practise in Angular to use immutable objects where possible to support accurate and efficient change detection, especially where arrays and objects are involved.

So in the example of AIS targets... the underlying Map object is updated in a targeted way but if used as the component data source change detection will not necessarily see the individual attribute changes and trigger an update.... hence building the current values into an immutable array and providing it as the data source.

That being said I am continuing to tune the 'message processing' now that the major performance obstacle seems to be resolved. Once we are happy it is resolved I will add the removal of stale AIS targets.
Just so we are all on the same page: Stale= no update in a prescribed period, so open suggestions as to what is considered a reasonable prescribed period as I know there are likely to be different opinions here.

[panaaj]

Commit #de7ff8a streamlines onMessage handling and also AIS target rendering.
Stale AIS targets (no update in the last hr) are removed.

[panaaj]

Commit #17f26a6 should now close this.

Active = last update received < 3 mins
Inactive= last update received > 6 mins
Removed when last update received > 9 mins

[joabakk]

This is sound practice for most use cases, but for a kiosk showing hourly updates worldwide from Marinetraffic or similar, I would like to have this user configurable.

[panaaj]

Fixed and available in 1.0.0-0 pre-release.