If you are running that close to full, then running more than one recommender might be a preferable solution. You can take one off-line, update it, bring it back, update the other. This decreases redundancy for a small period, but that is usually an acceptable risk.
On Fri, Nov 19, 2010 at 1:44 PM, Sebastian Schelter <[email protected]> wrote: > Good thing to talk about that issue, it's really not an ideal situation > to have FileDataModel need double memory at refresh time as it > effectively cuts in a half the amount of preferences that can be loaded > into per memory per machine. >
