Session data never needs to be in memory. It can be processed sequentially or using map reduce.
The item item data is all you need in memory. Sent from my iPhone On Mar 18, 2012, at 10:19 PM, Mridul Kapoor <mridulkap...@gmail.com> wrote: > On 19 March 2012 02:24, Ted Dunning <ted.dunn...@gmail.com> wrote: > >> Mridul, >> >> What is the humongous amount of data in Mongo? Is it really item->item >> links? Or is it session information? >> > > It is session information. So this should anyway exceed, I suppose. And in > my case, I need to pre-compute the item-item similarities. These would be > refreshed periodically, maybe three times a week. I then need a recommender > to run as a web-service, which would read from these pre-computed > similarities(should be stored in some persistent place, right?). Could you > suggest the way forward here, then. > > Thanks > Mridul
