3 ms·
You could wrap the transaction in a lock based on the player ID which you could do with Redis or Memcached with near-zero impact on performance. A good referen
by delano 14y ago
You could wrap the transaction in a lock based on the player ID which you could do with Redis or Memcached with near-zero impact on performance.
A good reference:
http://www.nateware.com/an-atomic-rant.html http://www.nateware.com/an-atomic-rant.html
- EvilTrout 14y agoThat introduces external dependencies though. Also, since the update has to occur anyway, I'd bet that my solution is faster than also making a call to another database for a lock.