###@###.### 2001-11-01
------------------------------

J2SE Version (please include all output from java -version flag):
  java version "1.4.0-beta3"
  Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta3-b82)
  Java HotSpot(TM) Client VM (build 1.4.0-beta3-b82, mixed mode)


Does this problem occur on J2SE 1.3? Yes / No (pick one)
  Yes

Operating System Configuration Information (be specific):
  Windows 2000 Professional SP2
  
Hardware Configuration Information (be specific):
  Dual PIII-600 w/512 MB of RAM


Bug Description:

java.awt.Fonts created via Font.createFont(Map) are cached based on their
presence in the specified Map (via the TextAttribute.FONT key) and not on the
values in the specified Map of TextAttributes. This is a problem as you draw
hundreds or thousands of character Strings creating a Font for each one and
disposing of it when you are done. Often the TextAttributes are the same for all
the Strings that you draw. This is very time consuming. Out testing has shown
that when you cache Fonts based on the Map of TextAttributes you will get a 4x
improvement in drawing speed.

Steps to Reproduce (be specific):

Attached the test program(FontCache.java) that demonstrates how mapinfo use
Fonts and the difference in speed between Sun's Font caching mechanism and
caching via the Map of TextAttributes.


Test results on my single PIII PC machine with W2K:

H:\CAP\bug\mapinfo>f:\j2sdk1.4.0-beta3\bin\java FontCache
fontcache - demonstrates the speed of MapXtreme Java's font caching versus Sun's
 font caching.
  Font caching is off.
  Time to create 8000 fonts: 2859 ms
                             ^^^^^^^^^
H:\CAP\bug\mapinfo>f:\j2sdk1.4.0-beta3\bin\java FontCache -fontcache
fontcache - demonstrates the speed of MapXtreme Java's font caching versus Sun's
 font caching.
  Font caching is on.
  Time to create 8000 fonts: 547 ms
                            ^^^^^^^^

Verified performance improve with jdk build 1.4.1-beta-b09, mixed mode on w2k and solaris.

###@###.### 2002-04-24