-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce GPU load #7
Comments
Could be worth a try: |
williamsyang-work
added a commit
to williamsyang-work/timeline-chart
that referenced
this issue
Jul 6, 2022
All PIXI.Applications are initiated on the PIXI shared ticker, allowing them to all be controlled simultaneously. PIXI.Ticker.shared is controlled via TimeGraphRenderController and RenderEvents. RenderEvents fires custom events that are handled by event handlers initiated in the RenderController. RenderController is created in the UnitController; this is only because we need one RenderController and there is already only one UnitController. RenderEvents currently fires start-render events in: - TimeGraphComponent on creation and update. - StateController when scrolling up/down Stop render is debounced at a 1500 timeout after start render. Fixes eclipse-cdt-cloud#7 Signed-off-by: Will Yang <william.yang@ericsson.com>
Merged
williamsyang-work
added a commit
to williamsyang-work/timeline-chart
that referenced
this issue
Jul 12, 2022
All PIXI.Applications are initiated on the PIXI shared ticker, allowing them to all be controlled simultaneously. PIXI.Ticker.shared is controlled via TimeGraphRenderController and RenderEvents. RenderEvents fires custom events that are handled by event handlers initiated in the RenderController. RenderController is created in the UnitController; this is only because we need one RenderController and there is already only one UnitController. RenderEvents currently fires start-render events in: - TimeGraphComponent on creation and update. - StateController when scrolling up/down Stop render is debounced at a 1500 timeout after start render. Fixes eclipse-cdt-cloud#7 Signed-off-by: Will Yang <william.yang@ericsson.com>
williamsyang-work
added a commit
to williamsyang-work/timeline-chart
that referenced
this issue
Jul 21, 2022
All PIXI.Applications are initiated on the PIXI shared ticker, allowing them to all be controlled simultaneously. PIXI.Ticker.shared is controlled via TimeGraphRenderController and RenderEvents. RenderEvents fires custom events that are handled by event handlers initiated in the RenderController. RenderController is created in the UnitController; this is only because we need one RenderController and there is already only one UnitController. RenderEvents currently fires start-render events in: - TimeGraphComponent on creation and update. - StateController when scrolling up/down Stop render is debounced at a 1000ms after start render. Fixes eclipse-cdt-cloud#7 Signed-off-by: Will Yang <william.yang@ericsson.com>
PatrickTasse
pushed a commit
that referenced
this issue
Jul 22, 2022
All PIXI.Applications are initiated on the PIXI shared ticker, allowing them to all be controlled simultaneously. PIXI.Ticker.shared is controlled via TimeGraphRenderController and RenderEvents. RenderEvents fires custom events that are handled by event handlers initiated in the RenderController. RenderController is created in the UnitController; this is only because we need one RenderController and there is already only one UnitController. RenderEvents currently fires start-render events in: - TimeGraphComponent on creation and update. - StateController when scrolling up/down Stop render is debounced at a 1000ms after start render. Fixes #7 Signed-off-by: Will Yang <william.yang@ericsson.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Even without any interaction, the Chrome profiler shows more than 50% load on the GPU.
Can we improve on that?
The text was updated successfully, but these errors were encountered: