LWN.net Logo

Linux TCO edge: Lower labor costs (ZDNet)

Here is a different perspective on the "total cost of ownership" issue on ZDNet. "In the survey, Linux admin salaries were slightly higher than Windows admins, with Linux at $71,400 per admin, and Windows at $68,500 per admin. But Linux admins took care of an average of 44 servers and Windows admins an average of 10. So the salary per processing unit was Linux, $12,010, and Windows, $52,060."
(Log in to post comments)

TCO: Arithmetic?

Posted Jan 5, 2003 9:15 UTC (Sun) by AnswerGuy (guest, #1256) [Link]


$71,400/admin/yr over 44 Linux servers = ~$1600 admin/yrs/server
$68,500/admin/yr over 10 Window servers = ~$6850 admin/yrs/server

... So the numbers cited here don't add up. The gist of it is
well taken, but someone ought to clarify where these numbers are
coming from.

Even if we multiply by 5 (which is a very long life cycle for servers
in this field) we only get ~$8k admin costs per Linux server (over
its "useful life" and ~$35k for each MS Windows server.

Arguably the Linux server *might* last for seven years (though they
will probably have had a couple of hard drive, memory and other
major component replacements in that time). The MS Windows server
almost certainly can't have its life extended for longer in most
mainstream business server applications --- because future MS
upgrades (which will be necessitated by client software upgrades
--- like incoming .NET and C# applications) will require far more
horsepower than the existing systems.

Certainly there are exceptions to these usable lifespans.

As a case in point, I'm running a 12 year old 386 system (with a
new hard drive after the previous one served for over ten years of
continuous use) as my mail and DNS server for a SOHO consulting
business. The system started on MS-DOS, ran briefly under Netware,
and the started life anew with the SLS Linux distribution. It's
been through Slackware, Red Hat 3.03 (through 5.2). S.u.S.E., and
finally Debian.

However these exceptions are not useful for mainstream business
surveys.

TCO: Arithmetic? Read the article & you'd understand.

Posted Jan 5, 2003 12:25 UTC (Sun) by Duncan (guest, #6647) [Link]

> $71,400/admin/yr over 44 Linux servers = ~$1600 admin/yrs/server
> $68,500/admin/yr over 10 Window servers = ~$6850 admin/yrs/server

> ... So the numbers cited here don't add up. The gist of it is
> well taken, but someone ought to clarify where these numbers are
> coming from.

From page two of the article: <quote>
Robinson compared the cost of "processing units"--the number of servers that
would be required to process 100,000 hits per day, and tracked the costs over
three years. [] The study found that Windows needed an average of 7.6 servers
for a processing unit, Linux needed 7.4, and Solaris needed 2.2.
</quote>

Note that it took slightly but not significantly more server power on the MS
platform to serve those hits and comprise a processing unit, than it did on Linux.
However, the big difference was in admin cost, and if you do the math based on
the "processing units" as defined in the study,and the fact that they found an MS
platform admin did ten servers, while a Linux platform admin could handle 44, you
come up with the numbers in the LWN quote, $12.01K for Linux, although the
absolute salary was a bit higher at $71.4K, $52.06K on MS, on a salary of 68.5K.

I found the following summary of three-year costs, from page three of the article,
equally interesting: <quote>
According to the study, the three-year cost of a 100,000-hit processing unit was
significantly different among the systems:

Solaris: $561,520
Windows: $190,662
Linux: $74,475
</quote>

MS was making hay for years on the fact that it was considerably cheaper than
commercial unix, as is shown above. Now, Linux is beating them at their own
game. If the above numbers are taken at face value, there's roughly a factor of
three difference between Linux and Windows, and between Windows and Solaris.
That means Solaris was close to 9 times the cost of Linux, over the three years!
Of course, one would hope the Solaris solution would last a bit longer than three
years, while both Linux and Windows were figured on x86 hardware, where that
three years is it's entire assumed usable life. Thus, the Solaris solution won't be
QUITE that much more expensive, over a longer period, say, if it lasts two x86
lifetimes or 6 years.

TCO: Arithmetic? Read the article & you'd understand.

Posted Jan 6, 2003 0:37 UTC (Mon) by iabervon (subscriber, #722) [Link]

The Solaris figures in the article are actually supposedly for Solaris on x86 hardware. Why
anyone would want to run Solaris on x86 hardware is beyond me, since it doesn't have the
advantages that Sparc Solaris has, and costs about as much to run. I'm actually mystified as to
how they managed to need less than a third the hardware to run Solaris as Linux; I can believe
that Linux isn't necessarily as fast, but a factor of three seems to suggest that there's
something else wrong.

TCO: Arithmetic? Read the article & you'd understand.

Posted Jan 6, 2003 14:34 UTC (Mon) by dougm (guest, #4615) [Link]

I was also confused. I think they must be using SPARC, because they also quoted a figure of one physical server per processing unit for Solaris, rather than three or whatever it was for Linux/W2K.

Linux TCO edge: Lower labor costs (ZDNet)

Posted Jan 5, 2003 20:42 UTC (Sun) by rickfdd (guest, #4519) [Link]

Maybe the server/admin discrepancy can be partially explained by the licensing cost of Microsoft. It affects the decision to buy new boxes for new applications or cram them on an existing servers. I'm glad I don't spend my days managing this packing.

My favorite jab against TCO marketing is Joe Barr's treatice on Audit cost.

Linux TCO edge: Lower labor costs (ZDNet)

Posted Jan 6, 2003 6:20 UTC (Mon) by einstein (subscriber, #2052) [Link]

No, it's the opposite of that, really. Microsoft's official "best practices" is to put one service on one windows pc server - or sometimes, one service on a "farm" of windows pc servers. To do otherwise is to risk more frequent blue screens.

Linux/Unix, on the other hand, loves being loaded up with processes. You have typically one or two unix/linux boxes handling a number of web domains, while with windows, you have a farm of windows pc servers handling a single domain.

Even if the new ms licensing issues cause windows admins to start to rethink the policies which have required many windows pc servers, these admin/server ratios have been generally known for some time - certainly long before there was any talk of ms licensing v6.

Linux TCO edge: Lower labor costs (ZDNet)

Posted Jan 6, 2003 1:42 UTC (Mon) by anand (guest, #414) [Link]

I was running a dotcom datactr+office of 100%linux machines (45 systems) single handed. (mail, dns, apache, firewalls, samba and such stuff).

Later (due to retrenchments) I had to work for a MS shop. Two of us (one MCSE and me) we running about 20 W2K servers.

I also see this kind of numbers in other firms. So the numbers quoted in the article seem pretty close to reality

Rgds,
Anand

Linux TCO edge: Lower labor costs (ZDNet)

Posted Jan 6, 2003 2:25 UTC (Mon) by rknop (guest, #66) [Link]

I was "sort of" running some 25 machines, in addition to a little "mini-Beowulf" of 5 machines, spending about 10% of my time on it while I was really supposed to be doing astrophysics research as a post doc. (Budget strapped, we ended up doing our own sysadmin. Fortunately, I knew what I was doing.)

I didn't have to do any DNS, but we did run a web server, a mail server, and lots and lots of NFS (which was a continuing nightmare in the Linux world back in the middle of the 2.2.x kernel series).

I cut corners and wasn't doing everything a "real" admin does, but still I think our machines were fairly well run; patches were kept up to date, and I think the systems were as secure as anything fully on the Internet can be. I could never have done it with Windows. A lot of the sysadmin was done by keeping scripts and a self-developed filesystem-based database that kept track of all changes from the base RedHat install. If there was a serious problem, I could reinstall RedHat, run the "customization" script, and 20-30 minutes have the machine fully back online and functional without a lot of futzing, and without having to open a single time consuming GUI.

I can easily believe that full time, a Linux admin could take care of 45 machines, with more services than I was dealing with, be they servers or workstations or both. (Servers require more work, but more workstations mean more users with their own ideosyncracies to deal with.)

(One thing I absolutely refused to do, even though people sometimes asked, was install a dual boot machine. I said that if they wanted a dual boot machine, they were on their own, even for the Linux side; I would give no support whatsoever. Being a post-doc and not a sysadmin, I had the freedom to make this stipulation.... I felt confident that I could keep track of Linux, but I didn't want to deal with the configuraiton and security concerns that would come with having Windows on the same machine. Plus, it was easier for me to run my admin scripts if I could make the assumption that unless there was a problem, all machines were up in Linux and on the net at all times.)

-Rob

What about the client?

Posted Jan 6, 2003 11:07 UTC (Mon) by Peter (guest, #1127) [Link]

I didn't notice any reference to the client machines. Perhaps some domains (hosting services, compute clusters) are dominated by servers but I think the vast majority of businesses have a lot more client machines than servers per se. And, of course, the sysadmin's job depends a lot on how the clients are configured.

What is the expected admin time for taking care of, say, 10 Linux servers and 800 Linux client desktops, compared to the same on Windows 2000? What about a mixed environment with Linux servers and legacy clients? Or vice versa (unlikely, sure, but Windows 2000 does include NFS, NIS and KDC servers)?

Then there's the thin client model, but that's already mostly covered as a special case of pure-server environment.

If I were running just a server farm with no pesky end user desktops to worry about, Unix is a no-brainer, at least to me. But, even aside from the thorny issue of whether it's possible to roll out Unix on the desktop without a peasant revolt, the TCO question is interesting and probably not so one-sided.

What about the client?

Posted Jan 6, 2003 18:46 UTC (Mon) by einstein (subscriber, #2052) [Link]

The city of Largo, Florida has 800 thin client desktops all running KDE from a monster Linux server. They have a very small sys admin team, whose beepers don't go off at night. Very low maintenance.

What about the client?

Posted Jan 8, 2003 19:32 UTC (Wed) by Peter (guest, #1127) [Link]

The city of Largo, Florida has 800 thin client desktops all running KDE from a monster Linux server.

Yes, but as I mentioned already, that's the thin client model which is really more like an all-server setup. I don't deny that it's an excellent way to run a railroad, if you can get away with it, but there are many places where fat clients are more appropriate, or even required. I was wondering how TCO would stack up between OSes in that situation.

What about the client?

Posted Jan 6, 2003 20:46 UTC (Mon) by tjc (guest, #137) [Link]

What is the expected admin time for taking care of, say, 10 Linux servers and 800 Linux client desktops, compared to the same on Windows 2000?

I would expect Linux clients to be less work to admin for a couple of reasons:

1) There wouldn't be all of the Windows specific viruses to deal with

2) The ability to control via user accounts which parts of the system a user can trash, and limit the software that they can install

What about the client?

Posted Jan 7, 2003 0:18 UTC (Tue) by einstein (subscriber, #2052) [Link]

ms windows does not include nfs or nis - unless you're saying that pc versions of nfs & nis servers are included in the "windows services for unix" add-on?

In any case, the unix emulator running on win doze did not impress me at all when i saw it at Linuxworld in the microsoft booth. It seemed to be mostly a broken toy, just something to earn a checkmark on a list, nothing that could actually be used for anything substantive.

What about the client?

Posted Jan 7, 2003 13:53 UTC (Tue) by Peter (guest, #1127) [Link]

ms windows does not include nfs or nis - unless you're saying that pc versions of nfs & nis servers are included in the "windows services for unix" add-on?

Yes, they are - at least in Windows 2000 Server. Actually I don't know if it's part of SFU or just the base install, but a colleague of mine who just installed Win2000 Server showed me the NIS server config, nestled right in there amongst all the rest of the Active Directory mess. And NFS client and server software is on there too.

I haven't tried any of it out, so I have no idea if it's the same sort of joke as the Unix tools on the NT4 resource kit, or if it's for real.

Copyright © 2003, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds