Path visualizer optimization (Orbit line)

[emackey]

In an offline conversation, @mramato mentioned that orbit lines were not well optimized. I think he was talking about PathVisualizer and/or related classes. I searched and couldn't find an issue on this, maybe it's tucked away on a roadmap someplace, but I didn't see it. Close if dup.

@mramato can you explain in more technical detail here what kinds of improvements are needed to get the best performance for scenes with hundreds of orbit lines?

[pjcozzi]

#932 plus probably more work at the entity level.

I suspect we can close this a duplicate with this and perhaps #1045.

[pjcozzi]

OK to close as duplicate?

[mramato]

As a duplicate with dynamic buffers? I would say no. There is a lot of inefficiency in PathVisualizer that would still need to be cleaned up even if we had dynamic buffers today.

[Lighfer]

Are there any solution ideas? I am experiencing a particularly low performance problem in the 2000 paths, and the performance problem is also caused by the PathVisualizer.
I'm not familiar with the cesium source code yet, but if there are any ideas, I am willing to implement it to see if I can solve the problem.