# FCGI and Apache2 on win performance problem

**URL:** <https://www.ruby-forum.com/t/fcgi-and-apache2-on-win-performance-problem/51927>\
**Category:** Rails\
**Created:** [January 9, 2006, 10:40am UTC](https://www.ruby-forum.com/t/fcgi-and-apache2-on-win-performance-problem/51927 "2006-01-09T10:40:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmihelac](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/5fc32e/32.png) [@bmihelac](https://www.ruby-forum.com/u/bmihelac)\
**Post date:** [January 9, 2006, 10:40am UTC](https://www.ruby-forum.com/t/fcgi-and-apache2-on-win-performance-problem/51927/1 "2006-01-09T10:40:43Z")

</div>

Hi all,  
I am having problems with FCGI and Apache2 on windows.  
The error I often receive is 500 error code response with logs listed  
down. I successfully use Webrick server and CGI (very slow). I had  
configured apache as is described in these document:  
[http://dema.ruby.com.br/articles/2005/08/23/taming-fastcgi-apache2-on-windows](http://dema.ruby.com.br/articles/2005/08/23/taming-fastcgi-apache2-on-windows).

Any suggestions?

Logs:

> C:/ruby/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi\_handler.rb:141:in  
> C:/ruby/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi\_handler.rb:52:in  
> `process!’
> 
> C:/ruby/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi\_handler.rb:22:in  
> `process!’  
> D:/rdocs/test/public/dispatch.fcgi:24  
> FastCGI crashlog is full of:  
> [09/Jan/2006:10:12:20 :: 952] Ignoring unsupported signal USR1.  
> [09/Jan/2006:10:12:20 :: 952] Ignoring unsupported signal USR2.  
> [09/Jan/2006:10:12:20 :: 952] Ignoring unsupported signal HUP.

–  
Bojan M.  
Informatika Mihelac, Bojan M. s.p. | [www.informatikamihelac.com](http://www.informatikamihelac.com)  
 → tools, scripts, tricks from our code lab: [http://source.mihelac.org](http://source.mihelac.org)

---

<div class="post-metadata">

**Author:** ![bmihelac](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/5fc32e/32.png) [@bmihelac](https://www.ruby-forum.com/u/bmihelac)\
**Post date:** [January 22, 2006, 3:00pm UTC](https://www.ruby-forum.com/t/fcgi-and-apache2-on-win-performance-problem/51927/2 "2006-01-22T15:00:41Z")

</div>

I am running into the same sort of intermittent errors. Wondering if  
there could be a but in the active record gem mysql adaptor with a dual  
CPU machine. Is your machine a dual?

If I repeatedly reload a page that does no database access, it never  
fails. However, the moment I do foo = MyTable.find(:first), I can get  
it to fail pretty quickly. I have tried using both MySQL 4.1 and MySQL5

Actually, though, in addition to FCGI not working the way you describe,  
I also see crashes with WebBrick on this machine. It never crashes on  
my development machine (Mac). Unfortunately, I have to deploy on  
windows.

Ray

Bojan M. wrote:

> Hi all,  
> I am having problems with FCGI and Apache2 on windows.  
> The error I often receive is 500 error code response with logs listed  
> down. I successfully use Webrick server and CGI (very slow). I had

---

<div class="post-metadata">

**Author:** ![bmihelac](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/5fc32e/32.png) [@bmihelac](https://www.ruby-forum.com/u/bmihelac)\
**Post date:** [January 26, 2006, 1:19pm UTC](https://www.ruby-forum.com/t/fcgi-and-apache2-on-win-performance-problem/51927/3 "2006-01-26T13:19:24Z")

</div>

Ray, no it is not dual machine and I didn’t have any problems when used  
Apache CGI or WebRick.

best,  
Bojan

---

<div class="post-metadata">

**Author:** ![bmihelac](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/5fc32e/32.png) [@bmihelac](https://www.ruby-forum.com/u/bmihelac)\
**Post date:** [January 26, 2006, 6:46pm UTC](https://www.ruby-forum.com/t/fcgi-and-apache2-on-win-performance-problem/51927/4 "2006-01-26T18:46:08Z")

</div>

A fix for a WEBrick concurrency issue was just checked into the trunk.  
[http://dev.rubyonrails.org/changeset/3454](http://dev.rubyonrails.org/changeset/3454)

This is probably worse on a dual CPU machine. Doesn’t affect FCGI  
though.
