Updating on disk had already proven to be too slow (each request requires a
pool of other related data, and an update to 3+ “objects”, plus there are
background jobs going on constantly to re-calculate scores and things). I
did a lot of benchmarking to get to the genserver implementation…The app
is really a lot like a game.
Maybe the approach I should go for is to use genservers to route requests
to the proper node, but use ETS to actually maintain the state of each
object. Any thoughts on that?
