A fairly serious performance regression appeared in the Cricket "D" build.
It is still present in "G".

The amount of startup footprint used during font initialization has increased by
about 300 K. It used to be around 380 K in 1.2 FCS (which was quite scarey enough
thank you) and has now risen to around 700 K. This is extremely serious.

Even more seriously, we are allocating around 8 K for each font in the system. My
NT system has a comparitively small nunber of fonts. We know from the JDK 1.2 beta3
experience that some customers have large numbers of fornts installed. For example,
James reports that Corel draw happily installs "a couple of thousand fonts".

We can't afford to have something that consumes several K per font.

We need to get font initialization back to JDK 1.2 levels for Cricket FCS.

graham.hamilton@Eng 1999-02-17