You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Karl Wettin (JIRA)" <ji...@apache.org> on 2008/04/12 18:49:06 UTC
[jira] Created: (MAHOUT-35) Benchmark performance of
Vector.iterator() when reusing Element instances.
Benchmark performance of Vector.iterator() when reusing Element instances.
--------------------------------------------------------------------------
Key: MAHOUT-35
URL: https://issues.apache.org/jira/browse/MAHOUT-35
Project: Mahout
Issue Type: Task
Components: Matrix
Reporter: Karl Wettin
Assignee: Karl Wettin
Currently a new instance of Vector.Element is created for each call to iterator.next(). The JVM pools this but we can always help it out.
See MAHOUT-34 comments.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MAHOUT-35) Benchmark performance of
Vector.iterator() when reusing Element instances.
Posted by "Sean Owen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen resolved MAHOUT-35.
-----------------------------
Resolution: Fixed
Fix Version/s: 0.2
Looks like this was long since fixed -- I see reuse of Element in the code already.
> Benchmark performance of Vector.iterator() when reusing Element instances.
> --------------------------------------------------------------------------
>
> Key: MAHOUT-35
> URL: https://issues.apache.org/jira/browse/MAHOUT-35
> Project: Mahout
> Issue Type: Task
> Components: Matrix
> Reporter: Karl Wettin
> Assignee: Karl Wettin
> Fix For: 0.2
>
>
> Currently a new instance of Vector.Element is created for each call to iterator.next(). The JVM pools this but we can always help it out.
> See MAHOUT-34 comments.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.