JEP submitted: Update Java2D to use the Marlin Renderer as the default Graphics Rasterizer

gerard ziemski gerard.ziemski at oracle.com
Mon Aug 31 15:29:50 UTC 2015


It's very exciting to see that we're addressing the performance issues of our currently existing Pisces 2D engine.

I'm not sure how detailed we want to have the JEP, but the following are the issues I would love to see the JEP go into 
a bit more detail:

#1 In the "Success Metrics" we say "significantly outperforms", but we're not committing to any hard numbers - do we 
have an expectation on how much better the new engine will be, that can be stated? Especially since we claim that the 
development version already meets this goal?

#2 What is the expected CPU usage allowed when scaling up in a multi-threaded environment - 2 threads probably do not 
mean 2x performance? Is Merlin allowed to use all threads, or does it have a limit on how many will be used? Can/should 
this be controlled via some sort of a runtime flag available to developers?

#3 Is Merlin's quality and accuracy high enough that it could one day replace the font rendered as well?

#4 Is Merlin performing well on both desktop and mobile platforms? Is such platform separation still needed?

#5 Would it be helpful to find an external use case scenario, in addition to the internal ones (ie. Pisces and Ductus), 
such as the performance of Adobe's Flash to compare Merlin's performance?

#6 In the "Alternatives" section, shouldn't we at least mention a GPU based 2D rendering?


cheers


On 08/27/2015 05:23 AM, Laurent Bourgès wrote:
> FYI, the JEP is waiting for Candidate review:
> https://bugs.openjdk.java.net/browse/JDK-8131760
>
> Best regards,
> Laurent
>
> ---------- Message transféré ----------
> De : "Laurent Bourgès" <bourges.laurent at gmail.com>
> Date : 24 juil. 2015 17:30
> Objet : JEP submitted: Update Java2D to use the Marlin Renderer as the
> default Graphics Rasterizer
> À : <graphics-rasterizer-dev at openjdk.java.net>, <2d-dev at openjdk.java.net>
> Cc :
>
>> Dear all,
>>
>> I submitted a JEP to use the Marlin renderer instead of Pisces to improve
> both performance, scalability and also quality.
>>
>> FYI Marlin is in development for few months within the graphics
> rasterizer project.
>>
>> Please look at the JBS bug JDK-8131760 for more details:
>> https://bugs.openjdk.java.net/browse/JDK-8131760
>>
>> Comments & feedback are welcome.
>>
>> Regards,
>> Laurent Bourges
>
>


More information about the jdk9-dev mailing list