You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2012/11/22 16:40:58 UTC

[jira] [Resolved] (CODEC-163) ColognePhonetic encoder unneccessarily creates many char arrays on every loop run

     [ https://issues.apache.org/jira/browse/CODEC-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Gregory resolved CODEC-163.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.8

{noformat}
commit -m "<action dev="ggregory" type="fix" issue="CODEC-163" due-to="leo141">ColognePhonetic encoder unneccessarily creates many char arrays on every loop run.</action>" C:/svn/org/apache/commons/trunks-proper/codec/src/changes/changes.xml C:/svn/org/apache/commons/trunks-proper/codec/src/main/java/org/apache/commons/codec/language/ColognePhonetic.java
    Sending        C:/svn/org/apache/commons/trunks-proper/codec/src/changes/changes.xml
    Sending        C:/svn/org/apache/commons/trunks-proper/codec/src/main/java/org/apache/commons/codec/language/ColognePhonetic.java
    Transmitting file data ...
    Committed revision 1412589.
{noformat}

                
> ColognePhonetic encoder unneccessarily creates many char arrays on every loop run
> ---------------------------------------------------------------------------------
>
>                 Key: CODEC-163
>                 URL: https://issues.apache.org/jira/browse/CODEC-163
>             Project: Commons Codec
>          Issue Type: Improvement
>            Reporter: Martin Rust
>            Priority: Minor
>              Labels: performance
>             Fix For: 1.8
>
>         Attachments: patch-CODEC-163
>
>
> The summary says it all.
> I've created a patch and have attached it.
> I've benchmarked a 10% performance improvement. Admittedly, I expected more, but other positive effects should be less strain on heap and GC.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira