You shouldn't be confused because you got it right :) Cheers
Michael Am 21.02.2011 um 15:40 schrieb Rick Otten: > Ok, I'm following this discussion, and now I'm confused. > > My understanding was that the (potentially very large) database is > replicated across all instances. > > If someone needed to traverse to something that wasn't cached, they'd take > a performance hit, but still be able to get to it. > > I had understood the idea behind the load balancing is to minimize > traversals out of cache by grouping similar sets of users on a particular > server. (That way you don't need a ton of RAM to stash everything in the > database, just the most frequently accessed nodes and relationships > associated with a subset of the users.) > > > > >> Hello JT, >> >>> One thing, when you say route requests to specific instances .. does >>> that >>> imply that node relationships can't span instances ? >> >> Yes that's right. What I'm suggesting here is that each instance is a full >> replica that works on a subset of requests which are likely to keep the >> caches warm. >> >> So if you can split your requests (e.g all customers beginning with "A" go >> to instance "1" ... all customers beginning with "Z" go to instance "26"), >> they will benefit from having warm caches for reading, while the HA >> infrastructure deals with updates across instances transactionally. >> >> Jim >> _______________________________________________ >> Neo4j mailing list >> [email protected] >> https://lists.neo4j.org/mailman/listinfo/user >> > > > -- > Rick Otten > [email protected] > O=='=+ > > > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
