[go: nahoru, domu]

Skip to content
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

☂️ Investigate performance differences between pipeline state object creation in OpenGL and Metal. #74631

Closed
chinmaygarde opened this issue Jan 25, 2021 · 2 comments
Labels
engine flutter/engine repository. See also e: labels. P2 Important issues not at the top of the work list team: benchmark Performance issues found by inspecting benchmarks team Infra upgrades, team productivity, code health, technical debt. See also team: labels. team-engine Owned by Engine team triaged-engine Triaged by Engine team

Comments

@chinmaygarde
Copy link
Member

This is an umbrella issue issue to investigate if there is a performance difference between the OpenGL and Metal backends when the pipeline state objects are being constructed, to quantify those differences and track any work necessary to bring parity between the two. Specifically, this is related to the work done in GrMtlPipelineStateBuilder::finalize. The scope of this issue is limited to ensuring parity between the backends. Moving the work outside the frame workload is tracked here. More context in the original issue asking for an investigation on Metal Binary Archives.

@pedromassangocode pedromassangocode changed the title Investigate performance differences between pipeline state object creation in OpenGL and Metal. ☂️ Investigate performance differences between pipeline state object creation in OpenGL and Metal. Jan 25, 2021
@pedromassangocode pedromassangocode added engine flutter/engine repository. See also e: labels. passed first triage team Infra upgrades, team productivity, code health, technical debt. See also team: labels. team: benchmark Performance issues found by inspecting benchmarks labels Jan 25, 2021
@Hixie Hixie added the P2 Important issues not at the top of the work list label Jan 25, 2021
@Hixie Hixie added this to Investigation in Early-onset jank Feb 22, 2021
@Hixie Hixie moved this from Investigation to Ideas in Early-onset jank Mar 29, 2021
@flutter-triage-bot flutter-triage-bot bot added team-engine Owned by Engine team triaged-engine Triaged by Engine team labels Jul 8, 2023
@zanderso
Copy link
Member

Closing this as obsoleted by past and upcoming work on Impeller.

@zanderso zanderso closed this as not planned Won't fix, can't repro, duplicate, stale Aug 11, 2023
@github-actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
engine flutter/engine repository. See also e: labels. P2 Important issues not at the top of the work list team: benchmark Performance issues found by inspecting benchmarks team Infra upgrades, team productivity, code health, technical debt. See also team: labels. team-engine Owned by Engine team triaged-engine Triaged by Engine team
Projects
Development

No branches or pull requests

4 participants