Bug ID: JDK-4641854 Java2D: Single threaded rendering

Type: Enhancement
Component: client-libs
Sub-Component: 2d
Affected Version: 5.0

Priority: P4
Status: Closed
Resolution: Duplicate
OS: generic
CPU: generic

Submitted: 2002-02-22
Updated: 2006-12-23
Resolved: 2006-12-23

The goal is to single-thread at the lowest-level of rendering to a
framebuffer device to reduce complexity of implementation and prevent
deadlocks and related artifacts.
Also some graphics hardware operates most optimally if accessed from a
single thread of a single process.

======================================================================

EVALUATION I think this bug report originally was a placeholder for planning purposes, but since then we have provided a single-threaded implementation of the OGL pipeline under a more specific bugid (6219284). We are also planning to update the implementation of our Direct3D pipeline on Windows to use the same single-threaded techniques (see 6389876). Since single-threaded rendering is not something that is provided generally in our Java 2D implementation, but rather at a lower level in certain specific pipelines, this bug can be closed (I'll close it as a dup of 6219284 for lack of a better option). For more on the magic of single-threaded rendering, see these two blog entries: http://weblogs.java.net/blog/campbell/archive/2005/03/strcrazy_improv_1.html http://weblogs.java.net/blog/campbell/archive/2005/07/strcrazier_perf.html

23-12-2006

EVALUATION Name: pr15447 Date: 02/22/2002 This feature has been added for Tiger release ======================================================================

11-06-2004

Duplicate :	JDK-6219284 - OGL: render on a single thread for improved reliability and performance
Relates :	JDK-6389876 - Java2D hw acceleration should be better integrated with future windows platforms