mahout-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <ted.dunn...@gmail.com>
Subject Re: Why do userid & itemid have to be long?
Date Wed, 01 Jun 2011 04:15:13 GMT
It makes the internals much cleaner to not repeat this conversion.

But how is it that this is taking a long time?  String -> lookup should not
be much longer than an array access, especially if you use the Mahout
collections or one of the dictionary types.

On Tue, May 31, 2011 at 7:50 PM, Mike Khristo <mikekhristo@gmail.com> wrote:

> Rather, how can I use string-based userid/itemid's without having the deal
> with the slowness associated with mapping them to a long?
>
> In the MongoDataModel, for example, significant time/overhead goes into
> converting the unique id's to long...  I'm still getting my head wrapped
> around mahout, but this seems like a significant limitation. I have to
> assume there's some logic behind the decision to restrict them to long, but
> i didn't find anything about it in Mahout in Action or the list.
>
> Thanks.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message