View Single Post
  #3  
Old 01-05-2010, 12:47 PM
mistwang mistwang is offline
LiteSpeed Staff
 
Join Date: May 2003
Location: New Jersey
Posts: 7,590
Start a fresh ruby process is very expensive, so it is not a good idea to let ruby process die frequently. Instead, LiteSpeed will keep one ruby process running, when new request comes, it will fork a child process to serve the request, and the child process quit after idling for a while. When multiple request comes in at the same time, the parent ruby process can fork multiple ruby processes immediately to serve all requests. That's the reason why parent ruby process does not serve any request directly.
Reply With Quote