Constructing a collator from rules is quite an expensive operation. In ICU 2.6,
code was introduced that will construct a collator for a locale from rules if
the image is not present or is stale.
It might be beneficial to have a cache for images of collators constructed from
rules, so that repeat constructions are faster.
On the other side, keeping any cache around involves a certain amount of book
It should be investigated if this stunt would be worth the effects, given the
usage model for collation.
02/06/04 14:52:55 weiv changed notes2
We do not build from rules any more when the binary is missing or mismatched, but we should LRU-cache loaded collators (or CollationTailoring instances).
As part of (ICU 54), CollationTailoring instances are cached in the UniversalCache.
Constructing a Collator from rules at runtime seems rare. I don't think we need to cache CollationTailorings for such Collators.
The code that provided the original motivation (build from rules when the bundle does not have binary data) was removed in ICU 53.