Recently I moved from windows servers 2003 32 bit and IIS6 to windows servers 2008 64 bit and IIS7. My experience was rather painful, windows 2008 seems like a wild animal after windows 2003 experience. 2008 has lots networking and scalability issues and it took me quiet a while and many tweaks and hacks to achieve reliability and good performace plus scalability and solve many issues.

If you own a windows 2008 server under some significant load from the web issues described in this post maybe relevant for you. Maybe it may save you some time in desperate searching around the net for solutions...

Before we continue to windows 2008 and IIS7 tips - some relevant info about IIS7.

IIS7 breaking changes

IIS7 introduced new integrated pipeline model where asp.net pipeline is integrated into IIS which has extensibility and performance benefits. This comes together with some breaking changes to configuration and asp.net.

Follow this link to learn more:

asp.net 2 breaking changes on-iis 7

OK, now some tips...

Disable static compression

IIS7 has static compression turned on by default and dynamic compression turned off by default. My first tip is to disable static compression (website - compression in IIS7 manager).

It can be the problem when you have static XML files on you server for example. XML files become unreadable by XML parsers with IIS7 static compression. Browsers and other 3rd parties will not be able to read them anymore because XML is malformed (possible bug?).

Change max concurrent requests per CPU setting

By default IIS7 has a limit of handling 12 concurrent requests per CPU and will queue requests above this limit. If you have some significant web load and many AJAX style requests to your server - this setting maybe very restrictive and it is hard to find out the root of the problem when you server performance is suddenly degraded.

See this post to get the picture how it can cause performance issues on your server.

Some relevant info about asp.net thread usage on IIS7 here:

asp.net thread usage on IIS7 and IIS6

Thomas Marquardt advice is to change this default limit. Recommended settings:

"All of this may be a little confusing, but for nearly everyone, my recommendation is that for ASP.NET 2.0 you should use the same settings as the defaults in ASP.NET v4.0; that is, set maxConcurrentRequestsPerCPU = "5000" and maxConcurrentThreadsPerCPU="0".

This is done by adding DWORD MaxConcurrentRequestsPerCPU to the registry under

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\2.0.50727.0

called MaxConcurrentRequestsPerCPU (DWORD). This key doesn't exist by default. Or/and in aspnet.config section which overrides registry setting (also doesn't exist by default) aspnet.config is here on windows 64bit:

%windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet.config

You need to add the following section under "configuration" section (here I used default values) - don't forget change maxConcurrentRequestsPerCPU to 5000.

< system.web>
    < applicationPool 
        maxConcurrentRequestsPerCPU="12" 
        maxConcurrentThreadsPerCPU="0" 
        requestQueueLimit="5000" />
< /system.web>

Disable offload network enhancements if you have network issues

Different unexplained network issue on your windows 2008 server could be related to TCP Chimney and related "networking enhancements" in windows 2008 and certain hardware vendors when hardware doesn't play well with these enhancements.

If you have networking problems similar to these below - try to disable these features.

Information about the TCP Chimney Offload, Receive Side Scaling, and Network Direct Memory Access features in Windows Server 2008

Related threads:

1. IIS 7 http status 400 errors
2. impacts to sql server workloads
3. the effect of tcp chimney offload on viewing network traffic

Set Connection "close" request header explicitly posting to AJAX web services

When moving from IIS6 to IIS7 integrated mode you may experience issues similar to below (POST request time-outs and request aborted errors) and all related to AJAX POST requests to IIS7 while AJAX GET requests don't have any problem.

Related threads (all unresolved)

1. a few "Request timed out" exceptions every day
2. "Request timed out" errors moving from IIS6 to IIS7
3. Request Timed Out on Windows Server 2008/IIS7
4. IIS7 Integrated Mode Request timed out

I experienced the same issue. Some HTTP POST requests got aborted in IIS7 pipeline and never reach server code. It can happen one per 1000 requests. However it may be still a significant number and if you have many users it can degrade performance for other requests.

In HTTPERR logs you can notice Timer_EntityBody errors related. POST requests usually arrive split in 2 segments: headers and following request body while GET requests arrive in one segment. On network monitor you can notice that server received POST request headers but request body never arrives to the server and after some timeout IIS aborts such request.

The solution is to set Connection "close" request header on the caller explicitly. Somehow IIS7 doesn't treat it very well, while IIS6 is able to handle missing Connection "close" header. Go figure.

Example for XMLHTTP javascript client:

oXmlHttp.setRequestHeader("Connection", "close");

Enjoy :)

Thanks for all who was around here in 2009 and helped us with great suggestions, feedback and support. We wish you all happy New Year!

Hello

We are moving to new servers and occasional brief downtimes are expected during December on our sites and apps. Sorry for the inconvenience.

As announced previously backup facebook inbox functionality is now available on Fosimo. It took some time until the app was whitelisted on Facebook in terms of reading users inbox permission but now it should be operational. If you already have Fosimo 1.0.8 it should work.

Download here. Hurry up because maybe it is the first app on Facebook which is capable of doing this. For now your inbox is saved in XML format.

Enjoy :)

Fosimo 1.0.8 is available. Fosimo is a desktop app for Facebook which helps you control your Facebook account without browsing through Facebook.

Facebook has rolled out several important features recently including new inbox functionality today and new authentication scheme for desktop applications a couple of weeks ago so there are new features and adjustments.

New in Fosimo 1.0.8

• Improved permissions configuration and authentication (supports recently introoduced "Publish Stream" and "Read Inbox" permission).
• Improved photo upload functionality.
• Improved set status (removed "is" verb). This is an old bug on Fosimo but finally fixed.
• Many fixes and enhancements.
• Backup facebook inbox: now you can backup your inbox on facebook to your hard drive with 1 click. Please note: Facebook is rolling out new inbox functionality now so it may take a couple of days until this feature is fully available for everyone.

Enjoy

I didn't try Windows 7 yet. But seems that Windows 7 inherited user access control feature from Windows Vista as is. It maybe useful info for people running MSIs on Windows 7.

I learned it because lifehacker linked yesterday to my 2-year-old post about MSI Error 2869 on Windows Vista where I explained the error and how to deal with it (lifehacker had the same MSI problem on Windows 7). In short — the error is caused by user access control feature and you need to run MSI from command line as administrator as a workaround (or patch the MSI). I was a bit surprised yesterday while reading that 2-year-old post since it seems very techy and it took me a while to fully understand it :). Good coverage after all...

Back in February 2009 we crossed 1 million users mark across all our applications on all platforms combined (link).

In July (or even in June) we reached 2 million. Right now the number is roughly 2243K total users (with more than 1 million users on Friendster alone).

Right now we have 13 applications with more than 50K users each.

Fosimo 1.0.7 is available. Fosimo is a desktop tool for Facebook which helps you control your Facebook account without browsing through Facebook.

New in Fosimo 1.0.7

• Quick launch on double-click and slowing down animated windows just like in a Fosimo.TR for Twitter lates version.
• New Facebook authentication scheme for desktop apps (which works through Facebook Connect) is implemented starting from Fosimo 1.0.7.
• Many small fixes and enhancements.

Enjoy

Fosimo.TR 0.5.6 is available for download. Fosimo.TR is a light and simple Twitter client for windows which helps you keep track of your Twitter account without browsing through Twitter.

New in Fosimo.TR 0.5.6

• My @responses: now one can view all @responses on twitter in real time (or "mentions" as twitter calls it). It is one of the items of the main menu.
• Quick tweet: double-click on the tray icon will open a tweet window for a quick tweet.
• When moving the mouse over animating icon it slows down. Users complained that small boxes move too fast and we finally address this issue slowing down each box after the mouse was over it.

We have more on our TODO list. We will roll up new versions regularly.

Download now!

Your feedback is appreciated. Don't forget to follow @fosimo on twitter. Enjoy.

Fosimo.TR 0.5.5 is available for download. Fosimo.TR is a Twitter client for windows which helps you keep track of your Twitter account without browsing through Twitter.

New in Fosimo.TR 0.5.5: friend list paging. Twitter has a limitation of 100 rows of data per API call therefore for those who have more than 100 friends on twitter (meaning people you follow) we implemented paging. I have 280+ for example.

Also we restored a click-on-animation functionality. Now one can click on animation and get their friend's details in a single click. This way people are able to retweet/reply in just 2 clicks.

A couple of small fixes included in this version as well.

Download now!

Your feedback is appreciated. Don't forget to follow @fosimo on twitter.