System Calls In Apache (Linux) vs IIS (Windows)

Mattias Geniar, Sunday, November 9, 2008 - last modified: Sunday, November 2, 2008

The following 2 pictures show a clear difference in system calls between a Linux' Apache, and a Windows' IIS. Draw your own conclusions. :-)

First up: Apache.

System calls for Apache

System calls for Apache

Followed by: IIS

System calls for IIS

System calls for IIS

They both seem chaotic, but the Apache one shows a lot more structure than the IIS one, which seems to be tangled up in its own web.


Hi! My name is Mattias Geniar. If you're interested in keeping up with me, have a look at my podcast and weekly newsletter. For more updates, follow me on Twitter as @mattiasgeniar.

SysCast podcast

In the SysCast podcast I talk about Linux & open source projects, interview sysadmins or developers and discuss web-related technologies. A show by and for geeks!

cron.weekly newsletter

A weekly newsletter - delivered every Sunday - for Linux sysadmins and open source users. It helps keeps you informed about open source projects, Linux guides & tutorials and the latest news.

Share this post

Did you like this post? Will you help me share it on social media? Thanks!

Comments

Andreas Sunday, February 1, 2009 at 01:08

well maybe this is the raeson why the IIS were so vulnerable back in the day as i guess that these systemcalls back there remained the same as now

Reply


Pierre Sunday, May 23, 2010 at 09:52

As G-WAN outperforms Apache and IIS by orders of magnitude in performances (for both static and dynamic contents) and footprint (the 100 KB G-WAN is a *native* Web App. Server offering full ANSI C scripts) it would be interesting to see the same graph applied to G-WAN.

G-WAN is available on Linux and Windows (where it beats IIS-7.0-nested-in-the-Windows-kernel).

Reply


sebastian Monday, December 19, 2011 at 20:58

nice! i only wish to know, is it a system call picture with all running-IIS Features? it look like!

Reply


Leave a Reply

Your email address will not be published. Required fields are marked *

Inbound links