<AWT Dev> RFR: 8260931: Implement JEP 382: New macOS Rendering Pipeline [v8]
prr at openjdk.java.net
Mon Feb 15 20:59:44 UTC 2021
On Mon, 15 Feb 2021 20:52:09 GMT, Gerard Ziemski <gziemski at openjdk.org> wrote:
>> Ajit Ghaisas has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains 20 additional commits since the last revision:
>> - Lanai PR#191 - 8261705 - jdv
>> - Lanai PR#190 - 8261706 - jdv
>> - Lanai PR#189 - 8261712 - avu
>> - Lanai PR#187 - 8261704 - jdv
>> - Lanai PR#186 - 8261638 - avu
>> - Lanai PR#185 - 8261632 - jdv
>> - Lanai PR#184 - 8261620 - aghaisas
>> - Lanai PR#182 - 8261547 - psadhukhan
>> - Merge branch 'master' into 8260931_lanai_JEP_branch
>> - Lanai PR#181 - 8261143 - aghaisas
>> - ... and 10 more: https://git.openjdk.java.net/jdk/compare/c8554bef...7b0b0dc4
> Marked as reviewed by gziemski (Committer).
> > > Thanks @gerard-ziemski for taking a detailed look at this.
> > > We do have an open bug to address this. Please refer [JDK-8259825](https://bugs.openjdk.java.net/browse/JDK-8259825).
> > Hi Gerard, expecting a process and parsing its output is definitely not ideal and that's why there's this open bug.
> > One thing that is under consideration is to equate >= 10.14 with Metal is available since as of 10.14 macOS won't install if a system does not support metal. We have no compelling reason to support metal on earlier releases anyway .. those are either already unsupported or barely supported and OGL will always be available there.
> I did not know that there already was a bug covering this issue.
> Your idea seems reasonable.
> More than just focusing on this immediate issue, however, I was hoping to raise the point of us starting adopting profiling tools to analyze our code (memory utilization, leaks, cpu/gpu profiling etc). A new feature that brings 10% benefit, but uses 50% more resources for example would probably not be a good investment. And to figure that we need to relay on some good tools and Xcode provides some.
There were actually tasks to do profiling of the memory footprint and look for leaks. We did not think it possible to be able to assert "Metal must use less memory than OpenGL" or dig into tiny differences but it was intended to find the big issues. See https://bugs.openjdk.java.net/browse/JDK-8237856
@prsadhuk maybe able to say how much of it was doing using Xcode.
More information about the awt-dev