Message6458

Author public.marvin
Recipients public.marvin
Date 2011-03-28.13:09:41
SpamBayes Score 6.4539705e-07
Marked as misclassified No
Message-id <1301317782.27.0.710588696533.issue1725@psf.upfronthosting.co.za>
In-reply-to
Content
The TRACE method in SRE_STATE.java has a comment saying "should get hot-spotted out".  Unfortunately, it is called "poorly" in many instances, like, 

 TRACE(0, ptr, "copy " + lo + ":" + hi +  " from " + mark_stack_base);

In this case, before the call, lots of StringBuilder operations occur.  It also seems that in my use-case (with a not particularly long running VM that gets restarted a lot) that hot spot doesn't ever decide to optimize anything.

Profiling my code shows a huge amount of time spent (9s) in SRE_STATE.SRE_CHARSET() with all of that in TRACE(), StringBuilder.append,<init>, and toString().

These TRACE statements should be removed or actually commented out.
History
Date User Action Args
2011-03-28 13:09:42public.marvinsetrecipients: + public.marvin
2011-03-28 13:09:42public.marvinsetmessageid: <1301317782.27.0.710588696533.issue1725@psf.upfronthosting.co.za>
2011-03-28 13:09:42public.marvinlinkissue1725 messages
2011-03-28 13:09:41public.marvincreate