Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Conversation

@gaaclarke
Copy link
Member

After having run a memory audit on Flutter Gallery I believe we can turn on wide gamut support by default for impeller. Here are the ramifications of this change:

  1. If an opaque surface is used and no transparent wide gamut images are used, there should be no change in performance or memory usage.
  2. If a transparent surface is used; the surface will take up 2x memory (ex 4MB on iPhone 7) and will have a runtime performance cost.
  3. If wide gamut transparent images are used, they will take up 2x memory. Opaque wide-gamut images will take up the same amount of memory.

Flutter gallery test results

Test 1

Steps:

  • Tap "Material"
  • Scroll down and back to "Cards"
  • Tap "Cards"
  • Scroll to bottom of "Cards" example

Notice that the card images are wide gamut, AdobeRGB.

Memory increase: 10.401 MB (+8.7%)

Test 2

Steps:

  • Just launch the gallery

Notice that there shouldn't be any wide gamut images.

Memory Increase: 1.22 MB (+1%, this is probably a fluke of measurement)

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the Flutter Style Guide and the C++, Objective-C, Java style guides.
  • I listed at least one issue that this PR fixes in the description above.
  • I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt. See testing the engine for instructions on writing and running engine tests.
  • I updated/added relevant documentation (doc comments with ///).
  • I signed the CLA.
  • All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@chinmaygarde chinmaygarde changed the title [impeller] Turned on wide gamut support by default [Impeller] Turned on wide gamut support by default. Feb 28, 2023
@gaaclarke gaaclarke marked this pull request as ready for review March 13, 2023 17:55
@gaaclarke gaaclarke requested a review from chinmaygarde March 13, 2023 17:55
@gaaclarke
Copy link
Member Author

We're getting to the point where we'll get better testing if we just turn this on. Anyone that runs into problems can just use the flag to turn it off.

Copy link
Member

@chinmaygarde chinmaygarde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd want to hold on this. In the last go/impeller-weekly, this was slated for iOS Preview Exit + 1 release. We just landed the Impeller flag flip test run towards the end of last week and are reasoning about the benchmark updates. I don't want to add another variable to those numbers right now. After the branch cut though, this lgtm.

@chinmaygarde
Copy link
Member

Closing this and putting it in the icebox so its off the triage queue. But we can re-open once the release train leaves.

@gaaclarke
Copy link
Member Author

Can I switch it back to a reopen it and switch it back to a draft so it is out of your review queue? I don't keep track of my closed PRs but drafts I do.

@chinmaygarde chinmaygarde reopened this Mar 23, 2023
@flutter-dashboard
Copy link

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

@chinmaygarde chinmaygarde marked this pull request as draft March 23, 2023 20:32
@gaaclarke gaaclarke marked this pull request as ready for review April 17, 2023 18:02
@gaaclarke gaaclarke requested a review from chinmaygarde April 17, 2023 18:02
@gaaclarke
Copy link
Member Author

I think this is ready now, no?

@chinmaygarde
Copy link
Member

I think this is ready now, no?

Yup yup. We discussed this in the last weekly and were waiting for you to be back. Let's land this ASAP. Can you give a heads up in go/flutter-chat when you do so we watch out for memory bench updates?

@chinmaygarde
Copy link
Member

The ci.yaml stuff was changed recently and needed a rebase. Just did one to kick off the presubs.

@bernaferrari
Copy link
Contributor

I'm kind of lost, but does this mean we should have a Color.p3() soon? Not sure what happens to current hex colors, or if this is "images only".

@gaaclarke
Copy link
Member Author

I'm kind of lost, but does this mean we should have a Color.p3() soon? Not sure what happens to current hex colors, or if this is "images only".

There is no plan to make any change to the Color class. This just effects loading wide gamut images, gradients and reading/writing pixels to ui.Image. You can't specify them when selecting the color of a widget, for example. We should make an issue for that if people are interested.

@bernaferrari
Copy link
Contributor

Oh, ok. Thanks!

zanderso added a commit that referenced this pull request Apr 21, 2023
auto-submit bot pushed a commit that referenced this pull request Apr 21, 2023
Reverts #39801

`customer: chalk` hit some rendering issues that was narrowed down to this: b/278976014
gaaclarke added a commit to gaaclarke/engine that referenced this pull request May 12, 2023
After having run a memory audit on Flutter Gallery I believe we can turn
on wide gamut support by default for impeller. Here are the
ramifications of this change:
1) If an opaque surface is used and no transparent wide gamut images are
used, there should be no change in performance or memory usage.
1) If a transparent surface is used; the surface will take up 2x memory
(ex 4MB on iPhone 7) and will have a runtime performance cost.
1) If wide gamut **transparent** images are used, they will take up 2x
memory. Opaque wide-gamut images will take up the same amount of memory.

## Flutter gallery test results

### Test 1

Steps:
* Tap "Material"
* Scroll down and back to "Cards"
* Tap "Cards"
* Scroll to bottom of "Cards" example

Notice that the card images are wide gamut, AdobeRGB.

**Memory increase:** 10.401 MB (+8.7%)

### Test 2

Steps:
* Just launch the gallery

Notice that there shouldn't be any wide gamut images.

**Memory Increase:** 1.22 MB (+1%, this is probably a fluke of
measurement)

## Pre-launch Checklist

- [x] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [x] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [x] I read and followed the [Flutter Style Guide] and the [C++,
Objective-C, Java style guides].
- [ ] I listed at least one issue that this PR fixes in the description
above.
- [ ] I added new tests to check the change I am making or feature I am
adding, or Hixie said the PR is test-exempt. See [testing the engine]
for instructions on writing and running engine tests.
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] I signed the [CLA].
- [x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel
on [Discord].

<!-- Links -->
[Contributor Guide]:
https://github.com/flutter/flutter/wiki/Tree-hygiene#overview
[Tree Hygiene]: https://github.com/flutter/flutter/wiki/Tree-hygiene
[Flutter Style Guide]:
https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo
[C++, Objective-C, Java style guides]:
https://github.com/flutter/engine/blob/main/CONTRIBUTING.md#style
[testing the engine]:
https://github.com/flutter/flutter/wiki/Testing-the-engine
[CLA]: https://cla.developers.google.com/
[flutter/tests]: https://github.com/flutter/tests
[breaking change policy]:
https://github.com/flutter/flutter/wiki/Tree-hygiene#handling-breaking-changes
[Discord]: https://github.com/flutter/flutter/wiki/Chat
gaaclarke added a commit that referenced this pull request May 17, 2023
relands #39801

forward fix for internal customers at cl/531288297

## Pre-launch Checklist

- [x] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [x] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [x] I read and followed the [Flutter Style Guide] and the [C++,
Objective-C, Java style guides].
- [ ] I listed at least one issue that this PR fixes in the description
above.
- [ ] I added new tests to check the change I am making or feature I am
adding, or Hixie said the PR is test-exempt. See [testing the engine]
for instructions on writing and running engine tests.
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] I signed the [CLA].
- [x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel
on [Discord].

<!-- Links -->
[Contributor Guide]:
https://github.com/flutter/flutter/wiki/Tree-hygiene#overview
[Tree Hygiene]: https://github.com/flutter/flutter/wiki/Tree-hygiene
[Flutter Style Guide]:
https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo
[C++, Objective-C, Java style guides]:
https://github.com/flutter/engine/blob/main/CONTRIBUTING.md#style
[testing the engine]:
https://github.com/flutter/flutter/wiki/Testing-the-engine
[CLA]: https://cla.developers.google.com/
[flutter/tests]: https://github.com/flutter/tests
[breaking change policy]:
https://github.com/flutter/flutter/wiki/Tree-hygiene#handling-breaking-changes
[Discord]: https://github.com/flutter/flutter/wiki/Chat
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

No open projects
Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants