Windows PCs vs. X Terminals: A Cost Comparison
The Mark O. Hatfield Library at Willamette University has used networked X terminals in its public and staff computing environments since 1995. The original workstations were NCD and Tektronix thin clients, but over the last two years, we have been replacing the systems with recycled PC hardware that otherwise would have been scheduled for replacement.
An X terminal is distinguished from a standalone personal computer in that X terminals rely on a networked computing model in which applications such as the desktop environment (window manager), Web browser and office software are hosted and run on a centralized application host located elsewhere on the network. The application host usually runs on heavy-duty server hardware, leaving the terminal workstation with the more trivial tasks of responding to input from peripherals such as the keyboard and mouse and drawing graphics to a monitor.
The Hatfield library currently has 25 of these X terminal systems deployed as specialized staff computers and kiosk-style public computing stations. They connect to two X client application hosts powered by x86-based PC server hardware running Red Hat Enterprise Linux, XFree86, XDM, the GNOME 2.4 desktop and the Mozilla Web browser.
In public computing environments, the model of centralized network computing has several advantages over traditional standalone workstations in that it:
Provides a no-cost alternative to expensive desktop deployment and cloning packages, such as Symantec Ghost, because new software is added to a single machine rather than deployed and run on each individual workstation.
Provides a centralized environment that is superior to standalone computing for backing up and maintaining user data as well as company proprietary data.
Enables institutions to maintain a homogeneous, flexible software environment even on PC hardware that has been purchased over a period of several years.
Extends the lifespan of personal computer hardware, yielding an overall decrease in investment in new hardware.
Is not susceptible to Windows-based viruses and spyware. Required security patches need be applied only to one system in order to update multiple systems.
As a rule of thumb, personal computing hardware at this institution is recycled out of the system after five to six years. Hardware and software manufacturers recommend a three-year purchasing cycle. The cost of replacing the 25 workstations deployed in our various labs and on staff workstations with new personal computers would be roughly $25,000.
Instead, we are replacing Windows with Linux on PCs that are six years old or even older and keeping those systems in service. In Addison to reducing the cost of new hardware and software purchases, it extends the return on investment of hardware already purchased.
Because these systems are being recycled out of service, there is no additional input cost for personal computing hardware. These literally are systems that otherwise would be thrown out.
Instead of purchasing new PCs, we instead make purchases on server hardware on a four-year cycle. Historically, one dual-processor x86 system can power applications for up to 25 X terminals.
By adopting this model, we have extended the lifecycle of our antiquated desktop hardware from seven to ten0 years, and we still are able to run current applications, including modern desktop environments, proprietary Java applications, Web browsers and office software.
Desktop PC model: 25 new PCs every three to six years.
Linux X Terminal Model: Two new application hosts (server hardware) purchased every four years with a two-year stagger. Adding recycled PCs as they become available.
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
If you already use virtualized infrastructure, you are well on your way to leveraging the power of the cloud. Virtualization offers the promise of limitless resources, but how do you manage that scalability when your DevOps team doesn’t scale? In today’s hypercompetitive markets, fast results can make a difference between leading the pack vs. obsolescence. Organizations need more benefits from cloud computing than just raw resources. They need agility, flexibility, convenience, ROI, and control.
Stackato private Platform-as-a-Service technology from ActiveState extends your private cloud infrastructure by creating a private PaaS to provide on-demand availability, flexibility, control, and ultimately, faster time-to-market for your enterprise.
Sponsored by ActiveState
| Speed Up Your Web Site with Varnish | Jun 19, 2013 |
| Non-Linux FOSS: libnotify, OS X Style | Jun 18, 2013 |
| Containers—Not Virtual Machines—Are the Future Cloud | Jun 17, 2013 |
| Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer | Jun 12, 2013 |
| Weechat, Irssi's Little Brother | Jun 11, 2013 |
| One Tail Just Isn't Enough | Jun 07, 2013 |
- Speed Up Your Web Site with Varnish
- Containers—Not Virtual Machines—Are the Future Cloud
- Linux Systems Administrator
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Senior Perl Developer
- Technical Support Rep
- Non-Linux FOSS: libnotify, OS X Style
- UX Designer
- Web & UI Developer (JavaScript & j Query)
- Android's Limits
- Reachli - Amplifying your
1 hour 5 min ago - excellent
1 hour 53 min ago - good point!
1 hour 56 min ago - Varnish works!
2 hours 5 min ago - Reply to comment | Linux Journal
2 hours 35 min ago - Reply to comment | Linux Journal
5 hours 1 min ago - Reply to comment | Linux Journal
9 hours 1 min ago - Yeah, user namespaces are
10 hours 17 min ago - Cari Uang
13 hours 48 min ago - user namespaces
16 hours 42 min ago
Featured Jobs
| Linux Systems Administrator | Houston and Austin, Texas | Host Gator |
| Senior Perl Developer | Austin, Texas | Host Gator |
| Technical Support Rep | Houston and Austin, Texas | Host Gator |
| UX Designer | Austin, Texas | Host Gator |
| Web & UI Developer (JavaScript & j Query) | Austin, Texas | Host Gator |
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?



Comments
This article is right in
This article is right in line with the reality when it comes to looking at costs of Windows vs. Linux. Clearly you can see the cost savings of Linux, and this article points out the reason why. I hope to see more articles like this, as people need to be educated on the value of Linux and how it can benefit individuals as well as businesses. I have gone into further depth in my own writing, on why this can be true:
http://members.apex-internet.com/sa/windowslinux
Re: Windows PCs vs. X Terminals: A Cost Comparison
I have recently completed conversion of WinPC's to X Term environment for several mortgage companies (3 seperate companies - total of 240 nodes in all). I must say I was a bit nervous at first but I am sure glad I made the switch. No more crashes. No more virus issues. I have a life again. Clients very happy. Do what you want. Say what you want. 'Hooked on Linux. Worked for me.' To my fellow MCSE's, better get certs on this. You'll be missing some big ops.
Re: Windows PCs vs. X Terminals: A Cost Comparison
X-terminals are nice if you never have to use portables. If people in a company need portables because they visit customers, work from home/remote office ..., X-terminal based solutions are never competitive in price, flexibility and ease of use.
Having a mixed environment of PC and X-terminals is a nightmare from the operational point of view; the IT department has to be trained and has to solve issues for both systems, which is a burden. We've tried it out and switched backed to PC-only systems
Re: Windows PCs vs. X Terminals: A Cost Comparison. Check out St
Granted, laptop don't fit into the thin client model.
However this is getting addressed the Stateless Linux project which
combine the best of both worlds.
It allow thin clients and with downloaded shadow images, laptops.
Dom
Re: Windows PCs vs. X Terminals: A Cost Comparison
What type of portables do you mean?
i'm using an old Tecra 8000/192MB RAM/20GB with low-cost RTL8180L WLAN, Linux 2.4, KDE 3.2. There's no problem accessing the Local AP and connecting to any X-Server.
BTW.: Installing Linux the first time on a up-to-date notebook is a nightmare. Using windows is an adventure every day, every time.
Re: Windows PCs vs. X Terminals: A Cost Comparison
mistake. you should switch your portables to debian like we did. okay, not asap, started slowly - man by man. first rh, now everyone uses debian. once we started to dump redhat with debian, well over half of the staff switched home machines to debian as well. now I use linux desktop about 8 years.
I alway wonder why people care about m$.
note: we are software developers. closed source, commercial. on linux, for linux. (no, we do not even use (link) gnu libc in our programs).
Re: Windows PCs vs. X Terminals: A Cost Comparison
Excellent case study...how can we contact Salvador to get more info for a similar project?
Rahul Chopra
Re: Windows PCs vs. X Terminals: A Cost Comparison
You can email me. speralta [at] progressivetrail.org
Re: Windows PCs vs. X Terminals: A Cost Comparison
The cost for new Client Hardware should be in the 15 years comparison. But even with this added cost the X-terminal approach will be still cheaper then the MS-Windows deal.
Some years ago the X-terminal market was dead. Now people are using PC hardware as X-terminal base. This idea is a big success. The pure X-terminals of old were to expensive because of low volume. The PC hardware is high volume and the X-terminal solution is again competive.
And you can have a silent workstation again - if you use a USB-stick in your PC X-terminal as harddrive replacement. This should be nice for a library.
use cluster
Hm, instead of buying dedicated twin cpu machine as x server, may be use can cluster those old pc together and serve the same purpose? Sure this will further drive down the cost :-)
Re: Windows PCs vs. X Terminals: A Cost Comparison
This was exactly what my former university (about 2 years ago) did. They had the "programming" lab setup using networked clients, where your experience was whatever the server was. The first year there, they were still running an old server in the backend, and it was frightfully slow whenever the whole class was logged in.
The following year, they had upgraded that single machine to a shiny new dual pentium. Voila, instant performance, no change of functionality or clients. From our point of view, the hardware hadn't changed, but suddenly the screens were fast, and there were more applications.
Now, the 'word processing labs' on the other hand were also upgraded to nice shiny new pentium machines. Didn't take long for us to (a: install every p2p client known to man, b: circumvent administrative access to install said software, c: ensure that these machines were left in a virtually unusable condition every other day). Believe it or not, some students get a kick out of doing that. Makes the art students life hell ;-), because I can just to type up my report on OpenOffice in the programming lab
Re: Windows PCs vs. X Terminals: A Cost Comparison
roflmao!
Re: Windows PCs vs. X Terminals: A Cost Comparison
Part of my job is to provide helpdesk support for a School District that runs both Windows and Linux Terminal Servers. There are approxamatly 80 schools. We have more linux Thin Client stations that we have windows stations. It is not that Linux is not getting used, on the contrary it is being used just as much or even more than the Windows workstations.
However I spend more helpdesk time providing support for the Windows workstations than support for the Linux Thin Clients.
The Linux Thin clients are allot easier keeping up-to-date. I update the software on the Terminal Server and all thin clients instantly get the new software. I just run the Debian "aptitude" program and I can easily install/upgrade/remove software from a lab of 30-50 computers.
We purchase re-cycled $40 "Thin Clients". However our thin clients are getting fatter (eg P450) so we developed some sofware to do load balancing between the server and the client based on the client's CPU speed and RAM.
We do spend a bit more money on our Servers and Switches.
Our thin clients have a huge selection of free educational and business software. Just check out: http://www.debian.org/distrib/packages
I have heard many arguments regarding open-source vs closed-source ... But so far students seem to prefer having a wealth of free Linux software over a limited locked down windows station with few and expensive software. Teachers like Linux solutions because there are less chrashes, no viruses, no spyware, no kids snooping where they shouldn't be etc.
Linux to me represents:
- Less Licences
- Less Helpdesk Calls
- Easier To Keep Up-To-Date
- Easier To Remotely Administer
- More Controll
- More Flexibility
- More Software
- More Satisfied End Users
I manage Windows and Linux and Linux is easier to Manage.
Nothing to argue about in our School District.
----
Windows XP SP2 - Just trying to catch up to what Linux has had for a long long time... (Firewall, Automatic Updates, and Virus Protection).
----
"Dear Microsoft, please include Automatic Updates to ALL my software on my computer through windowsupdate.com. Don't just upgrade the operating system. Please see Debian Linux for an example. Thanks"
Re: Windows PCs vs. X Terminals: A Cost Comparison
I think a better comparsion should be made between the Windows Terminal Server and X Terminals.
Windows Terminal Server & X Terminals
Ok,
You were right! A better comparison between your examples!
Re: Windows PCs vs. X Terminals: A Cost Comparison
Nice article, we actually run our entire manufacturing operation on
linux desktops using remote x and recycled hardware. It is our experience and we can back this up with proof is that we spend less than a hour per month in maintenance excluding hardware issues. We recently started just buying neoware boxes for the client end as they are cheap and it is totally plug and play. If we wish to recycle a pc we use a hacked slack cdrom to boot x and straight to the server, this cut our deployment time of recycled hardware from a hour to seconds. I am absolutely shure I can turn up a 200 node existing network in a single day that is including loading and configuring the servers.
Just turn on xdmp on a redhat cluster and throw cd's in the client drives, done deal!
Re: Windows PCs vs. X Terminals: A Cost Comparison
Good article.
Salvador, how is your mom?
Say hi to her and the 2 dogs.
Re: Windows PCs vs. X Terminals: A Cost Comparison
Additionally, as the plan is now described, could not have been devised at the beginning of its intended project due to many of its critical pieces not existing.
I'm not sure which pieces you suggest were not available. A cursory view of the author's work shows that the project started with FVWM as the window manager, and Netscape as the browser. That they have migrated to newer WM and platform is no reason to discount the cost-benefits of a project that now appears to be nearly 10-years old for the sort of public workstations described in the article.
Re: Windows PCs vs. X Terminals: A Cost Comparison
From my experience in with PC's over the past twenty or so years, it seems that projections based on using primary hardware beyond three to five years have proved to be futile.
Sure, you can have something that runs. But what service is it providing to its user base. Or, on the other hand, what services is it not providing to its user base. If the intent is a cheap, reliable, and supportable system that can access a centralized base if information, telnet access from text only terminals is the way to go. If, instead, the goal is to provide a full featured modern internet experience, new hardware and fresh, easily replaceable, hard drives will be in order.
For most organizations, the proposed solution would not fit the bill. Additionally, as the plan is now described, could not have been devised at the beginning of its intended project due to many of its critical pieces not existing. This practice of redesigning and managing obsolesce can be administratively intensive and frequently leads to unsupportable pet networks.
As a fifteen year cost analysis, I think that this information is misleading at best. It may accurately represent the projected costs of maintaining this installation for the next five years, but it does not reflect a transferable model that can meet a typical organization
Re: Windows PCs vs. X Terminals: A Cost Comparison
"telnet access from text only terminals"
http://www.starfall.com/
sweet! roflmao
sweet! roflmao
Re: Windows PCs vs. X Terminals: A Cost Comparison
"If the intent is a cheap, reliable, and supportable system that can access a centralized base if information, telnet access from text only terminals is the way to go. If, instead, the goal is to provide a full featured modern internet experience, new hardware and fresh, easily replaceable, hard drives will be in order. "
Duh, you DORK, it is fully integrated GUI environment. It's not a dumb terminal like you are thinking. What an idot?
A wise man once said " It is better to be thought a fool. Than to open ones mouth and PROOVE it!!!"
Re: Windows PCs vs. X Terminals: +
Original poster, we're all here to learn so please share with us your wisdom.
What specifically would you recommend?
Regards,
JeffC
Re: Windows PCs vs. X Terminals: A Cost Comparison
Sure, you can have something that runs. But what service is it providing to its user base.
In a setup like this the service provided by the clients is totally independant of the client hardware. The clients do no processing and only send key clicks mouse movements and get screen updates from the central server. Thus any old piece of junk client will perform as well as any other high end client. I use a similar system with 24 terminals and they have neither hard disks nor floppies installed as both are totally unnecessary.
Re: Windows PCs vs. X Terminals: A Cost Comparison
To be fair (I have a couple of machines running as X-terminals using LTSP) some old junk is a bit too old to be much use. It mostly comes down to the video card, which needs to manage enough resolution and colours to run a vaguely modern desktop. The first random box I tried to use only had 256K of video ram (640x480 in 256 colours or 800x600 in 16), which is no use these days. You need 800x600x16bpp as a minimum now (2MB RAM) and preferably a lot more. And you do need a decent server to run modern desktops for more than a couple of boxes. BUt bearing those caveats in mind I'd agree that the system is excellent, and very reliable and easy to maintain, especially if the server is a debian box
Re: Windows PCs vs. X Terminals: A Cost Comparison
Actually, I agree in part. By using this setup with a fast network link, the X-term setup would indeed "deprive" you of several things:
--Aging and slow browser like IE.
--Worry about individuals defeating the Windows insecurity system to install potentially malicious programs.
--Relatively frequent downtime while various patches, patches of patches, and updates are applied while praying they have not broken some essential service.
Personally, I am quite happy to "suffer' this kind of deprivation.
Re: Windows PCs vs. X Terminals: A Cost Comparison
I don't think you understand the concept here, when you say that the users of X terminals will be deprived of a rich internet experience. The users will have the same experience as if they were to have their own full system. I have used this setup quite often to save time and money.
Re: Windows PCs vs. X Terminals: A Cost Comparison
You obviously have been to exposed only to the Windows model. This setup sounds exactly like what the organization needs and an X server-client model its a great solution. Not every organization has to be a slave to the M$ hardware cycle.
Re: Windows PCs vs. X Terminals: A Cost Comparison
...the goal is to provide a full featured modern internet experience...
That is exactly what this setup is capable of providing. It can provide whatever service the server is capable of. The server needs to have greater resources than individual stand alone workstations would have to have, but the experience will not be limited by the hardware used for the terminals.
Re: Windows PCs vs. X Terminals: A Cost Comparison
From my experience in with PC's over the past twenty or so years, it seems that projections based on using primary hardware beyond three to five years have proved to be futile.
Perhaps that's because you've never been exposed to the networked X model. So long as the PC is only being used to render graphics to a display, with the applications powered by a centralized host system on a fast network, there is no reason why a given PC can't be adequate for 10 years or longer. As I understand it, these folks don't even need to muck about with hard drives.