On Tue, Feb 28, 2012 at 9:46 PM, Yanni Chiu <[email protected]> wrote:
> On 28/02/12 2:48 PM, Mariano Martinez Peck wrote: > >> >> Yes, object caching is NOT a problem itself, it is a feature of Glorp or >> whatever. If what you use (like Fuel) is slow, then it may require some >> tunning. It can be caching object or not. What I suggest is that you >> stress your system with big data sets and you will see if you really >> miss object caching or not. >> > > It not a speed issue. It's about how big the image gets if all the on-disk > objects get pulled into memory. The Glorp cache had a max cache size and > LRU policy, IIRC. > > > If I understand you correctly, then what you are talking about is not caching objects but rather lazy loading. You mean when Glorp lets some proxies of the loaded graph so that they can load the rest of the graph later on? -- Mariano http://marianopeck.wordpress.com
