We’ve stumbled upon my favorite problem I can’t talk about. :-(
-
The clusters effectively create something of a voronoi pattern too, and it seemed like a good opportunity for LODing updates. In a neighboring cluster? Get every 2nd update. Neighbor's neighbor? Every 4th update. And so on.
Although, I do think that it's better for all this to be on one process, rather than a process per k-cluster, just for the headache of replicating across server boundaries. Instead, I'd be interested in seeing a process own a subsystem.
-
-
I would want the whole point of the clustering to be that you wouldn’t need to mirror data at all for the computation of the interaction, just to pass data on the results to the clients for notification.
-
Aka, you are “close enough” to see the combat taking place next cluster over, but not directly affect it, so you can get lossy or delayed information about it.
- Näytä vastaukset
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.