Forums | Chat | News | Contact Us | Register | PSU Social |
PSU: Don't let friends join the MLWA.
Forums | Chat | News | Contact Us | Register | PSU Social |
Home | Forum | Chat | Wiki | Social | AGN | PS2 Stats |
|
|
Thread Tools | Search this Thread | Display Modes |
|
2013-03-19, 04:56 PM | [Ignore Me] #1 | ||
now that´s some excellent communication!
thanks for the detailed info! most gamedevs just say "we fixed it" and that´s it. nice we get the opportunity to understand a few things that are happening behind the scenes! and congratulations on catching this bug!
__________________
***********************official bittervet********************* stand tall, fight bold, wear blue and gold! |
|||
|
2013-03-19, 07:56 PM | [Ignore Me] #3 | ||
Major
|
Sounds like you maxed out the database server's RAM and the game was running at write speed of the disk system?
Every time a player wants to repair their sundy, they'd have to wait for the disk to finish writing the new value before they can add the next repair tick . . . The disk heads are busy writing an excessive number of saves, so read access is impaired. At the same time you lose read speed between disk and cache, the cache is constantly getting flushed to make room for all the character saves in RAM, leading to extra time spent reading, slowing down the writes, creating a viscous spiral. The result is it takes a long time for clients to get update information from the database. Last edited by Fenrys; 2013-03-19 at 08:07 PM. |
||
|
|
Bookmarks |
Thread Tools | Search this Thread |
Display Modes | |
|
|