String call stats
gback at cs.utah.edu
Wed Feb 9 15:58:15 PST 2000
To complete the picture, and to evaluate the possible benefit
of the utf8 alternative, it would also be necessary to study
- how many of them are 7bit representable (for which charAt() would be
- how long the strings are and how often strings are copied during
construction or concatenation in the String and StringBuffer classes ---
this is where you not only save in space, but also in time.
In addition, it would be necessary to know how much time is spent in
charAt() vs. in those other methods, not just how often they're invoked.
Do you have an intuitive explanation as to why there's so many calls
to charAt() in kjc, for instance?
More information about the kaffe