Awesome, I will give ReloadFromJDBCDataModel a try. How does this particular data model update itself on database changes? Does it just happen periodically and if so, can this rate be change easily?
Lastly, will calling clear(userId) on a recommender frequently be bad for performance? I'm assuming with such small data amounts that the actual recommendation algorithm is quite speedy and that the DB is really the big bottleneck? On Wed, Jul 13, 2011 at 2:11 AM, Sean Owen <sro...@gmail.com> wrote: > That's all correct, it reads a lot. But you can avoid a lot of it by using > caching wrappers. > You also don't need to dump to a file. Use ReloadFromJDBCDataModel. > > On Wed, Jul 13, 2011 at 9:57 AM, Vitali Mogilevsky > <vit...@playedonline.com>wrote: > >> Hey, >> I got the same problem, of slowness while using MYSQL data model, after a >> small research and looking into mysql's query log, revealed that user - >> user >> recommendation just floods the database with thousands and thousands of >> requests. >> and thats on small database. >> for now Im dumbping the database into file, and using filedata model which >> works much faster >> >> >
