<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://forums.iis.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:cs="http://blogs.iis.net/"><channel><title>IIS 7 - FastCGI Module</title><link>http://forums.iis.net/1104.aspx</link><description>Questions related to the FastCGI module for IIS7</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>Re: General FastCGI question</title><link>http://forums.iis.net/thread/1906012.aspx</link><pubDate>Sat, 06 Jun 2009 01:15:39 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:1906012</guid><dc:creator>sergeia</dc:creator><slash:comments>0</slash:comments><comments>http://forums.iis.net/thread/1906012.aspx</comments><wfw:commentRss>http://forums.iis.net/commentrss.aspx?SectionID=1104&amp;PostID=1906012</wfw:commentRss><description>&lt;p&gt;FastCGI module will start Perl interpreter in new process when the first request will come, then it will keep it running for configuratble timeout, so inside of this timeout next request could be served by the same process. If you have more then one request waiting, FastCGI will start more processes with Perl, up to configurable number in total. That&amp;#39;s how FastCGI works. That said, configuration of Perl for FastCGI could be tricky.&lt;/p&gt;
&lt;p&gt;There is another scalable solution -- you could use Perl connected to server through ISAPI extension. We recommend this for Perl, not FastCGI. You could see details here: &lt;a href="http://blogs.iis.net/wadeh/archive/2009/04/13/running-perl-on-iis-7.aspx"&gt;http://blogs.iis.net/wadeh/archive/2009/04/13/running-perl-on-iis-7.aspx&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;--Sergei&lt;/p&gt;</description></item><item><title>General FastCGI question</title><link>http://forums.iis.net/thread/1899181.aspx</link><pubDate>Thu, 02 Apr 2009 19:55:45 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:1899181</guid><dc:creator>tbbatccc</dc:creator><slash:comments>0</slash:comments><comments>http://forums.iis.net/thread/1899181.aspx</comments><wfw:commentRss>http://forums.iis.net/commentrss.aspx?SectionID=1104&amp;PostID=1899181</wfw:commentRss><description>&lt;p&gt;I currently have a site running on IIS 7.0 (and 6.0 in some places) that uses a PERL script in between the browser and the program that runs in the background.&amp;nbsp; I am using Activestate perl.&lt;br /&gt;&lt;/p&gt;&lt;p&gt;When a web request is made, a PERL job is spawned, then when my background program runs, it also spawns a job, the background program ends, then the perl job ends with the results sent to the browser.&amp;nbsp; This is not PHP.&lt;/p&gt;&lt;p&gt;I want to try an speed up the process and was looking into whether FastCGI would be an answer where I would not spawn a new job for each PERL run .&amp;nbsp; All the posts/installs I have seen have more to do with PHP.. &lt;/p&gt;&lt;p&gt;My questions, is FastCGI something I can use for this purpose?&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description></item></channel></rss>