CesiumGS / CesiumGS/cesium

Polyline performance

Open
#4,738 1 comment 0 reactions 0 assignees View on GitHub
category - polyline category - vector data onramping priority - high type - bug
Dominant language
JavaScript
Stars
15.7k
Forks
3.9k
Avg merge
4d 6h
Merged PRs (30d)
34

Description

After creating lots of polylines, it seems a lot of time is spent each render in PolylineCollection.update -> createCommandLists, even though nothing changes.

Easy to reproduce by running this gist in sandcastle: https://gist.github.com/YousefED/092aa2e48ca8ac4518b5b5c39e1c1682

Wait for everything to load, then open Chrome inspector, and run the profiler:

![image](https://cloud.githubusercontent.com/assets/368857/21069952/62069540-be7f-11e6-9021-a0a7c3ff5224.png)

Contributor guide

Open the contributing guide

Research direction

Start with PolylineCollection.update and its createCommandLists call, then reproduce the issue using the linked Sandcastle gist. Profile the render loop in Chrome after everything loads and compare the time spent when the polylines are unchanged; done means avoiding the reported repeated cost without changing rendering behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
computer-graphics, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.