I've managed to get a rails app working under IIS using FastCGI, however I've run into a bit of a snag. As a test I have a client program send 10 simultaneous requests to the same rails page (simple render 'hello world')
However when I slowly ramp up and get 10 ruby processes sitting idle on the webserver I can get all 10 simultaneous requests to complete successfully. I'm not sure if I would want a way to always have at least N workers or if there needs to be a way to get ruby.exe to start faster?
Thanks