Entity zone vs object container

Originally posted by


I’m curious about the same question, but note that the beauty with a graph db is that even though a carrack full of cargo, vehicles and players represents a huge amount of entities, all it takes to transfer it from one zone (i guess i should say “zone host OC”) to another is to change one vertice. I.e. the same amount of data to update than passing a Pico from one zone to another.

Yes, exactly. This is one of the major advantages of the entity graph. Re-parenting operations, such as attaching/detaching entities or changing their zone, are cheap operations as they only involve removing the “edge” to the old parent and adding one to the new parent. The cost of this on the database this isn’t affected by how many entities are attached to or inside the one being re-parented.

Parašykite komentarą

Ar esate pasirengę pradėti Star Citizen kelionę?