[
https://issues.apache.org/jira/browse/HTTPCORE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841933#action_12841933
]
Oleg Kalnichevski commented on HTTPCORE-216:
--------------------------------------------
Tony,
Are you still interested in working on this issue or shall I close it as
WONTFIX?
There are benchmarks you could use to measure the impact of your changes on
HttpCore performance
http://wiki.apache.org/HttpComponents/HttpCoreBenchmark
http://wiki.apache.org/HttpComponents/HttpClient3vsHttpClient4vsHttpCore
Oleg
> Custom implementation of parseInt and Integer.toString
> ------------------------------------------------------
>
> Key: HTTPCORE-216
> URL: https://issues.apache.org/jira/browse/HTTPCORE-216
> Project: HttpComponents HttpCore
> Issue Type: Sub-task
> Reporter: Tony Poppleton
> Priority: Minor
> Fix For: 4.1-beta1
>
>
> The parent task shows that a hot spot is the CharArrayBuffer.substringTrimmed
> method, and in a number of places it is only called to be able to parse an
> integer from the buffer using the Integer.parseInt(String str) method in the
> Jave libraries.
> This is a generalization of one of the patches in HTTPCORE-212 that was just
> addressing this issue in one place.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
