I stumbled upon a question about fastcgi-mono-server concurrency on Server Fault and thought I’d do some digging around. Initial checks using a couple of open tabs in the browser and Firebug seemed like there was some level of blocking, and only one page was served as once.
I had a look at the code and it appears to be fully supported so I devised an experiment to test it end-to-end. My experiment was to put a 10-second Sleep in one of my views, then hit two pages, one with the Sleep and then one without. If the system supports concurrency then the one without should render quickly many times while the other is waiting.
I tried this and a first the results looked bad, however, I was hitting both pages in the same browser. So I hit the Sleepy page on my desktop and hit the unaffected page on my mobile and it’s clear that concurrency is supported as my mobile was able to refresh the page several times while my desktop was waiting for the Sleepy page.
So, happy days, one fastcgi-mono-server process supports multiple simultaneous connections and processes the requests concurrently.
Solomon Hykes is probably most famous for being the founder and former CTO of Docker. Docker revolutionised the way we package, run and distribute server applications, so when Hykes starts a new venture, it's worth checking out.Discover More
I recently set up a Terraform project which I wanted to run on a regular schedule. There are a number of ways to achieve this, but I decided to package the project as a Lambda function and schedule it with…Discover More
I recently configured Single Sign On (SSO) from our Google accounts to AWS. AWS SSO is the recommended way to configure SSO across multiple AWS accounts, yet Google is not a supported identity provider. However, this simply meant that there…Discover More