In a recent startup performance analysis, the initialization of the
font infrastructure took a large percentage (about 25%) of the overall time to start
a simple AWT app. The Java2D font code was recently re-architected and
optimized, which could mean that the current bottlenecks lie in the i18n
code (such as loading the font config file).