Tracked down a few rogue processes on my machine which were eating all the memory. Killed them and profiling is now working.

16% of the time to serve the chart goes in looking up index values of keys in arrays. At the moment that's implelented using a linear search, so if we have to look up n keys we're looking at n-squared efficiency. Will replace that with a reverse-lookup hashtable to speed it up.

Another 16% goes in initializing the two fonts as I noted earlier.

15% goes on retrieving the dtable.

10% goes to the initialisation of java word-breaking classes so the chart can build text blocks.

At the moment, it takes about 7 seconds to retrieve a chart.

T
- posted by Tim Bruce @ 3:05 PM