2011-02-21, 04:19 PM
SaptaZapta Wrote:Huh?
Normal databases flush (force write) every completed transaction to permanent storage. Obviously I have no idea how Nexon configured their database, they might be saving I/O time by buffering several transactions at at time, but they have to be outright absurd if they "roll back" more than a second due to power out.
Note that "saving the database" in this case doesn't require exporting it (i.e., exporting the whole thing to a safe copy).
This is only relevant if you were actually playing the game in the database, which you're not.
The game is played in resident memory on the servers and only saves to the database at various intervals and triggering events.
Anything still in active memory when power goes out would not have been capable of committing.
Any transactions still committing when the power goes out would've been capable of completing from the transaction logs when the db comes back up, but depending on how hard the down was it'll have to run consistency checks and may have corrupted pages, which can result in significantly larger rollbacks becoming necessary.
It's not having what you want - It's wanting what you've got.
