Resium Optimization Notes

I'm hoping that there will be a way to optimize our resium applications. Specifically, in DWD we're rendering large networks in the browser (as opposed to pre-defining and storing in Ion). This works well enough for now, but has the potential to slow down quite a bit.

Polyline Caching

This link has some interesting information, though no straight answers. Maybe we can use Cesium to generate the first-cut of the 3D network entities, then store them in a local file to read from going forward?

https://community.cesium.com/t/polyline-caching-for-better-performance/14252/4

The final answer in that link:

• use wms to show points and labels if they are not changing positions, cache em, for interactivity use getfeatureinfo, google it:
• https://cesium.com/learn/cesiumjs/ref-doc/WebMapServiceImageryProvider.html
• use point primitives if your icons are not visually different than others, for dynamic icons:
• https://cesium.com/blog/2016/03/02/performance-tips-for-points
• you can support performance by explicit rendering:
• https://cesium.com/blog/2018/01/24/cesium-scene-rendering-performance/
• also for javascript use async operations instead of blocking operations
• You can use primitive api but it won’t help you much unless you find your in house solution. It is not that much performant after all.

Real-time Data

At first glance, this post seems relevant to our needs:

https://community.cesium.com/t/best-approach-to-process-lots-of-real-time-data/3545