Databases
StackOverflow2013
Postsdbo
POPhusion Passenger spawning problems
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPhusion Passenger spawning problems
    primarykey
    data
    text
    <p>I am working with a Rails 3RC app and using Phusion Passenger for the first time. It takes about 30 seconds to start up the app on the first request and here is the typical memory consumption for each ruby process in my app:</p> <p>PID &nbsp;&nbsp;&nbsp;&nbsp;VMSize&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Private&nbsp;&nbsp;&nbsp;Name<br> 18161 263.5 MB 75.4 MB Rack: /rails_apps/my_app/current</p> <p>Is that typical memory consumption? My app is about 11MB ( &lt; 4MB if you dont include my /public assets).</p> <p>It runs fine after the first request if there is one user, but I run into problems when I run some of my custom stress testing scripts, and also when I use my search suggestion feature which makes a bunch of quick ajax calls(which I expected, because the next request comes thru before the first one finishes). Here is what I find odd.. the server starts spawning Ruby threads which take an additional 30 seconds to load, but no other requests can go thru while the spawning is taking place. Just to double check, I tested with browsers on other networks while the processes were spawning just to make sure it was not something specific to my local machine (like all requests being served from one process). These browser requests had to wait until all the new spawns were complete.</p> <p>So my question is.. is this the typical behaviour of Passenger? Waiting on spawning before any other request can come thru? From looking at the documentation I would think that the other request would be handled by idle ruby processes while the spawning was happening. Here are the versions I am using in case you guys are aware of any incompatabilities. Thanks in advance! I really don't want to go back to Mongrel ;-)</p> <p><strong>my setup</strong><br> Quarter slice Rackspace Cloud (4GB RAM &amp; 1/4 of dual quad core)<br> CentOS 5.4<br> Rails 3.0RC<br> ruby 1.9.2dev (2010-05-31 revision 28117) [x86_64-linux]<br> Passenger 2.2.15 with mongrel </p> <p>nginx config options:<br> passenger_max_pool_size 30;<br> passenger_enabled on; #in / location block.. </p> <p>I tried conservative spawning and I am seeing the same behavior.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjohnmcaliley
    1. USjohnmcaliley
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPhusion Passenger spawning problems
      1. USmadh
      1. VTFavorite
    1. COI guess this is the expected behavior of Passenger. According to the Passenger blog: "Previously, when application processes are being spawned, Phusion Passenger is unable to handle HTTP requests until the processes are done spawning, because Phusion Passenger is holding the lock on the application pool while this is happening." I find it hard to believe that Passenger could be used on an app that has a high traffic. It could take 5 minutes for an app to respond after a restart. Aside from that Passenger looks good.. looking forward to v3. guess I have to stick w/ mongrel for now.
      singulars
      1. POPhusion Passenger spawning problems
      1. USjohnmcaliley
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload