开发者

Issue with passenger

Recently our ruby on rails application was upgraded to 2.3.8. We also replaced Mongrel/Mongrel cluster with Phusion Passenger during upgrade.

Whenever we try to deploy our application, it seems to be responding faster initially but response time gradually increases. We also noticed that cpu usage on the database box spiking to 400% and lot of requests waiting in global queue. This seems to be happening only in our production environment.

Can anyone let me know how I should go about debugging this issue?

Is there anyway we can restrict the number of connections between passenger and DB?

Also开发者_StackOverflow中文版 is there a way we can setup connection pooling in passenger?

Thanks,

Sivakumar.


I don't think the issue is with Passenger. If you are having a large spike on your DB box CPU, your issue probably lies there. Without more information about your database it's hard to give you specifics, but here are a few things you could try:

  1. Run top and check how much of your total memory the mysqld or other database process is consuming. If this amount is not high then you probably need to tune MySQL settings to take advantage of the RAM on your DB box.
  2. Analyze your running database queries with the mytop command. You might have some queries that are hogging all of your system resources or causing lots of swapping.
  3. Look through your MySQL slow log and see if you have queries that are taking over 1 second to run.
  4. Check your database engines. Are you using MYISAM and/or InnoDB? You might need to tune your database differently so that it can allocate the proper amount of memory and resources to each engine.
  5. Consult a DBA. They'll be able to take a look at your usage and application and tell you more definitively if the issue lies with your database or application.

P.S: I would recommend upgrading to Passenger 3, it performs better than Passenter 2.

0

上一篇:

下一篇:

精彩评论

暂无评论...
验证码 换一张
取 消

最新问答

问答排行榜