I appreciate the response and effort, thank you.
Performance with 1 satellite is great. I don't have specific metrics but the map is usable with multiple satellites, 1 orbit showing. Satellite data has 30s number of satellites but our javascript picks and chooses to only show between 1-15 satellites.
I am testing with Firefox v24.x and v31.x. Rendering all 30+ satellites
without orbits in Firefox has no problems. The performance hit occurs when multiple orbits/paths are set to visible. Setting the path to visible in the initial CZML file to load results in the same performance hit. Seems like the Firefox version may have some performance impacts; I'm not familiar with the difference in Firefox versions.
There is a significant improvement in performance when the path.resolution is set to a very large number to reduce interpolation (this is my understanding from the CZML Content page). With this property set to 10000000.0, rendering up to 6 orbits is ok; problematic when going over 6 satellites and their orbits. With interpolation reduced in Cesium, the path is not as smooth but that is expected. Is there a way to completely turn off interpolation of paths?
The CZML file for each satellite does not define any path.leadTime and path.trailTime elements. The position seem to be enough to render an accurate orbit for each satellite. Would not having the lead/trailTime affect performance?
One mitigation thought would be get the position elements and draw them as point/lines/polylines. Does anyone have any inputs on this approach?