Okay, that makes sense. Would that be a server-side cache, or a
client-side
cache?
There are no server-side caches (other than the OS disk cache).
Ok, that's what I gathered before, was just checking.
I believe I've already succeeded in getting a client-side persistent
disk-based
On Jan 17, 2013, at 10:31 AM, Claudiu Saftoiu csaft...@gmail.com wrote:
What I don't understand is that this doesn't seem to work in the long run.
Just before writing this email I ran a view that required a simple query
after not having restarted the server in a while, and it took a minute
Thanks, Jeff! I'll check out that cacheDetail stuff and see if I simply
have too few objects being stored (though I thought 5 million would be
enough...)
Further, after having preloaded the indices once, shouldn't it preload
quite rapidly upon further server restarts, if it's all in the cache
