Linux Saves Money and the Numbers Prove It
A few days ago, Cybersource, the company I work for, released a study undertaken on the relative operating costs of running a mid-sized business on Linux and free software on the one hand, and Windows and Microsoft applications on the other. We've had a significant response to this study from many industry news organisations, industry players and individuals. What I'd like to discuss here is both the context within which this study originated and the methodology and results which precipitated.
First, a little history. While our firm has been using Linux for almost the entirety of its ten-year history, (preceded by a stint with Minix no less), we have been recommending Linux server and network infrastructure solutions for only about six years and line-of-business desktop solutions for about three years. In all circumstances, we want to know that Linux could solve the business problems of a client before we proffer a solution recommendation. The Linux server solutions business has been going strongly, but uptake of Linux desktops among business customers has been slower. The past nine months, however, has seen a dramatic increase in the number of existing and potential new customers, indicating that they are looking seriously at large-scale, non-infrastructural deployments of Linux desktops and terminals. Many of these customers approached us with the question: "How much will we save if we move groups, departments or the whole company to Linux?" We didn't have an answer for them then. We do now.
One of the other prime motivators in our undertaking this project was as a response to Microsoft's claims that the cost of software licensing was a virtual non-entity in the overall calculation of IT budgetary expenditure, accounting for a mere few percent. Our experience with many clients indicated otherwise. We began with our first study, released late last year.
This study looked at the differences in software license costs between Linux and Windows, for 50, 100 and 250-user organisations. We included the types of core applications that most organisations need: workstation operating systems, office productivity, network infrastructure servers, file, e-mail and database servers as well as intranet, internet and e-commerce systems. As you can imagine, Linux easily defeated Microsoft's platforms and applications in a license cost comparison. This study was well received, but some of our readership recommended we look beyond just software license costs. We agreed. To gain the attention of financial and non-IT managers, we needed to provide a holistic 'real world' model, encompassing hardware, networking, staff, consultants, internet fees and sundry other cost components. Thus, this new study provides such a comparison.
We opted to base the costs on the IT needs of a 250-user organisation. We believe this would provide a reasonable indicator and gnomon from which to calculate IT costings for larger enterprises, as well as smaller firms. We decided to run two models, representing organisations that are buying everything from scratch and organisations who will use their existing hardware and cabling. For our green-fields model, we specified the servers based on our experience with equivalently sized customers' sites. We set the per-node network connection cost (inclusive of all cabling, switches and hubs) to a set figure and specified the workstation hardware on current generation business-class systems from a name-brand vendor that supports both Linux and Windows. We applied this same total hardware and cabling cost to both the Linux and Windows platform models.
For all the prices upon which we based our final calculations, we provide full details for the configuration of the hardware, a vendor-sourced URL, as well as a method by which we arrived at costs. We wanted to make sure that our own results could be verified or repudiated, thus enhancing the study. This theme ran throughout our work in general. We avoided all instances of cost incursion for factors that we could not provide complete verification for or that were at all disputable. We believed this would tarnish the overall results and weaken the paper's impact. We also wanted to run the model over the industry-accepted norm of a three-year IT equipment purchase/deploy/use and decommission cycle. This will hopefully allow the vast majority of enterprises whose own processes follow this cycle to apply the study's results directly to their IT-budget spreadsheet projections.
Other cost factors included in our calculations are staff wages, consultants' fees, costs for line-of-business software, the purchasing of specific technical applications, internet connectivity and a miscellaneous costs category as a final "catch-all". The figures we arrived at (based on re-using existing equipment) were $733,973 US for a Windows/Microsoft solution and $482,580 US when using Linux and free software, a saving of $251,393 US or 34.26%.
When the model requiring totally new hardware was computed, the Microsoft-platform solution cost $1,042,110 US, and Linux came in at $790,717 US. This implies a 24.69% reduction. It also shows that outfitting and running an organisation with brand new servers, networking, workstations and choosing Linux software is comparable in cost to keeping all the old equipment and purchasing a Windows platform solution. In view of the forthcoming licensing changes that Microsoft will soon bestow upon its customer base, whereby most organisations will need to repurchase all their existing Windows systems and applications at non-upgrade retail prices, this scenario will become very common.
The other interesting factor that came out in our research, is that IT professionals who have solid Linux skills appear to be paid a premium over correspondingly attired Windows-platform specialists--obviously good news for those who are presently on track towards Linux Professional Institute or RHCE accreditation or who have a strong leaning toward professional Linux and free software services. It must be remembered, however, that even with this cost disparity, the organisaton that opts for a Linux solution will manage to slash instantiation and operating costs severely.
In fact, it is this final point that now needs to be expounded. If, as the study has shown, many, perhaps most, organisations can accrue substantial financial benefits through the partial or total adoption of Linux and open source software, what remains to convince this group to move wholesale to Linux? Are existing implementors of IT within these organisations the remaining roadblock? Are they concerned about, as Australian art historian Robert Hughes famously pronounced during a corresponding period within the art world, "the shock of the new"? Would faster progress be made if these results were presented to financial and non-IT executive company officials, in the language and format they know and understand, rather than an IT staff? Would many of the businesses worldwide presently suffering economic hardship (and shedding staff) benefit financially from such a move to Linux? I welcome your responses.
Con Zymaris is CEO of Cybersource Pty. Ltd., a long-standing IT and internet professional services company.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- My +1 Sword of Productivity
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide