[
https://issues.apache.org/jira/browse/MAHOUT-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640268#comment-13640268
]
Gokhan Capan commented on MAHOUT-1193:
--------------------------------------
Ok, here are the updates:
I modified the code a little (made it run and modified as I had commented
previosly), and did some tests within the real application that I mentioned int
the user list.
Performance of get and sets (bigger is better):
DenseMatrix > SparseMatrix (with dense rows) > BlockSparseMatrix > SparseMatrix
(with sparse rows) > SparseColumnMatrix
Performance difference between SparseMatrix with dense rows and
BlockSparseMatrix is small.
One drawback of SparseMatrix might be that you need to specify the rowSize in
advance (which means you need to set a boundary for your row indices). This
wasn't a problem for me, but it's worth mentioning. With this version of
BlockSparseMatrix, there might also be a memory overhead depending on
blockSize.
I decided to go for SparseMatrix with dense rows for now, but I also work on
BlockSparseMatrix code (thanks to the flexible schema).
> We may want a BlockSparseMatrix
> -------------------------------
>
> Key: MAHOUT-1193
> URL: https://issues.apache.org/jira/browse/MAHOUT-1193
> Project: Mahout
> Issue Type: Bug
> Reporter: Ted Dunning
> Attachments: MAHOUT-1193.patch
>
>
> Here is an implementation.
> Is it good enough to commit?
> Is it useful?
> Is it redundant?
--
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
