Andrey -- I am glad you will be implementing fetch plan for local storage. BTW: odbuser2 and I seem to be concerned about opposite things. They want to make sure everything in the fetch plan *is* returned. I want to be sure *nothing more* than in the fetch plan is returned.
I am concerned about not instantiating any more objects on the java heap than necessary. If the fetch plan limits what I pull in to only what I ask for, then I can use a smaller heap, and avoid GC issues. A smaller heap in turn leaves more RAM on the machine for direct memory. This all assumes I correctly understand the OrientDB caching model :) -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
