Gamling.org bottleneck

I have found that the bottleneck for Gamling.org is on Mongodb.

I think there is a problem with Passenger forking. I have to try its solution first.

Right now I'm figuring out how to optimize it.

Here is the CPU usage: