Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
During profiling of Tapestry framework I found that AbstractStringBuilder.expandCapacity is called very frequently.
There is a patch that get rid of creation StringBuilder with following calls of expandCapacity (which allocate memory and copy current content into it).
I have to thank Dmitriy Ilyin, who helped me to investigate the issue and to find the simplest solution (actually we get a little bit less code while improving performance).
With this improvement time per request decreased on 0.5ms (1% of overall time)on our test. All measurements were done with apache benchmark after warm up phase.
Attachments
Attachments
Issue Links
- relates to
-
TAP5-2476 Improvement of TapestryInternalUtils.encodeQuoted
- Closed