Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

Re: Question on design for FastCGI

by sundialsvc4 (Abbot)
on Oct 15, 2012 at 17:22 UTC ( #999134=note: print w/ replies, xml ) Need Help??


in reply to Question on design for FastCGI

Consider the approach taken by RPC::Any.   The request is quickly classified according to some criteria ... it could be part of the URL, part of the request, or some combination ... and a processing module for that kind of request is located, dynamically brought into memory if it’s not already there, and given the work.   It is a simple yet flexible design, and, best of all, it is already implemented by someone else.

The FastCGI protocol is simple and flexible, and it can be applied in a lot of different ways.   I have used it among back-end service processes as well as front-end FastCGI worker bees.   Apache modules normally use a very simple strategy for apportioning out work among processes, but they don’t have to be simple strategies.

As Anonymous said, you want to pay a lot of attention to the actual workloads that your site must deal with, and constantly observe as a basis for your fine-tuning.


Comment on Re: Question on design for FastCGI

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://999134]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (6)
As of 2014-12-21 20:20 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (107 votes), past polls