fastcgi - Perl benchmark between FCGI and PSGI -


What do I know about the FCGI protocol, the first time when the application is called, it loads it in memory, runs it, returns the response to the server, ends the reaction, but the application does not end, If it continues in memory, then the next request will be compiled in the memory copy of the application to process this request.

Reading about the PSGI Protocol, it seems that it is going to do the same thing.

My question is, my assumption is correct, they are similar to the speed of application for requests per second.

Even if they do the same thing, I see that there is a command line option to enable FCG in the plack-up.

You are asking to compare between apples and fruits, your question does not understand much .

There are various underlying mechanisms that you can use to deploy a web application written in Perl.

  • This is a standalone CGI program
  • It can run under mod_perl
  • It can run under FcGI
  • etc. ...

The problem is that for each deployment system you need to change the way you write your program. This means that you need to know that you can start writing code Before mod_perl targets, say. It also means that transferring an application between these different deployment methods is non-trivial.

This problem solves PSGI. Instead of writing a CGI app or a mod_perl app or FCGI app, you write an app that targets the PSGI protocol. You can deploy exactly the same app under CGI, mod_perl or FcGI (or several other deployment methods).

If you use your PSGI app to use the FCGI handler, then this FCGI app. But to run it as a mod_perl app later it is simple to move. Or to run it as a standalone server like Storman.

Does this help everything?


Comments

Popular posts from this blog

java - org.apache.http.ProtocolException: Target host is not specified -

java - Gradle dependencies: compile project by relative path -

ruby on rails - Object doesn't support #inspect when used with .include -