I recently put some new benchmarking utilities on the server that make it easier to see what is causing the most database load.
As it turns out, these query your stats to find out which song you are in. Then each time they query EVERY SINGLE LEVEL YOU HAVE PLAYED and then do score arithmetic to see if you have a FC or AAA on that song.
The file that calculates this, by itself, is responsible for over half of the queries going into the server and is singlehandedly killing the query cache. It is responsible for anywhere between 10 to 70% of the server load at any given time. As such, I have disabled it until I can write a better system to calculate these.
As it turns out, these query your stats to find out which song you are in. Then each time they query EVERY SINGLE LEVEL YOU HAVE PLAYED and then do score arithmetic to see if you have a FC or AAA on that song.
The file that calculates this, by itself, is responsible for over half of the queries going into the server and is singlehandedly killing the query cache. It is responsible for anywhere between 10 to 70% of the server load at any given time. As such, I have disabled it until I can write a better system to calculate these.






Comment