Loading...

XML

Word

Printable

Type: Task
Resolution: Withdrawn
Priority: P4
Fix Version/s: internal
Affects Version/s: internal
Component/s: client-libs
Labels:
- common
- design
- lanai
- metalOSX
- sn_44
- sn_45
- sn_46
- sn_47
- sn_48
- sn_49

Subcomponent:
2d
CPU:

x86_64
OS:

os_x

To implement Metal Rendering pipeline in Java2d - either of below architectures can be followed :
1) Architecture option - 1 : Based on OpenGL Rendering Pipeline implementation of Java2d uses a single threaded RenderQueue to process graphics commands.

2) Architecture option - 2 : Based X11Render Pipeline implementation of Java2d uses direct rendering without single threaded RenderQueue.

This task is to evaluate differences/pros/cons of above options.

Things to consider would be :
1) Performance sampling of render calls
2) possible limitations in implementation using Metal APIs

blocks

JDK-8224046 ☂ Metal Graphics API Implementation

Resolved

is blocked by

JDK-8227664 Disable additional RQ.flushNow() that hogs the AWT-EventQueue thread

Closed

relates to

JDK-8230641 MTLRenderer_FillSpans method needs to be optimized by reducing total number of drawPrimitives calls

Resolved

JDK-8230837 MTLRenderer_DrawParallelogram method - can be optimized by combining 4 drawPrimitives calls

Resolved

JDK-8231614 Avoid passing of redundant vertex 'z' data to vertex shader

Resolved

JDK-8231456 Check possibility of usage of shaders to generate vertices in required format

Closed

JDK-8231883 Combine adjacent primitive draw calls to issue a single draw call with multiple data

Closed

(2 relates to)

There are no Sub-Tasks for this issue.

Assignee:: Ajit Ghaisas

Reporter:: Ajit Ghaisas

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2019-06-03 03:18

Updated:: 2020-02-05 02:29

Resolved:: 2020-02-05 02:29

Details

Description

Attachments

Issue Links

Sub-Tasks

Activity

People

Dates