You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <ui...@incubator.apache.org> on 2009/09/15 18:05:57 UTC
[jira] Updated: (UIMA-736) Performance improvement, Findbugs
reduction - replace new Integer(xxx) with Integer.valueOf(xxx), same for
byte, short, etc.
[ https://issues.apache.org/jira/browse/UIMA-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-736:
--------------------------------
Fix Version/s: 2.2.2
> Performance improvement, Findbugs reduction - replace new Integer(xxx) with Integer.valueOf(xxx), same for byte, short, etc.
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: UIMA-736
> URL: https://issues.apache.org/jira/browse/UIMA-736
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Affects Versions: 2.2.1
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Trivial
> Fix For: 2.2.2
>
>
> Findbugs reports lots of uses of new Integer(xxx). These can be replaced with Integer.valueOf(xxx) unless there is a need to have a unique instance of the object. This is not the case (at least in the ones I examined) - for instance, non of these were being used as a synch. lock. Replacing with valueOf allows Java to cache and reuse frequent values, so reduces garbage collections.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.