RFR 8150778: Reduce Throwable.getStackTrace() calls to the JVM
coleen.phillimore at oracle.com
Fri Mar 11 23:49:24 UTC 2016
On 3/11/16 6:36 PM, Aleksey Shipilev wrote:
> On 03/08/2016 01:55 AM, Coleen Phillimore wrote:
>>> Aside: see the last experiment, avoiding StringTable::intern (shows in
>>> profiles a lot!) trims down construction costs down even further. I'd
>>> think that is a worthwhile improvement to consider.
>> Hm, this is an interesting experiment. I've been looking for a better
>> way to store the name of the method rather than cpref.
> I did some preliminary work for storing class names (those are easy,
> since Class.name is already there on Java side). Would be nice to handle
> both method names and source files, because we are looking at some nice
> Can you pick it up, and follow up further?
Yes, I think caching String classname on Class<?> might be also helpful
for the StackWalk API.
My impression was that the performance of Throwable.getStackTrace()
wasn't super critical since it's used in exceptional conditions. Let me
I linked the bug I care about to this.
More information about the core-libs-dev