| |||||||||||||
|
| |||||||||||||
Samba beats Windows (vnunet)Samba beats Windows (vnunet)Posted Oct 14, 2003 1:17 UTC (Tue) by gdt (subscriber, #6284)In reply to: Samba beats Windows (vnunet) by einstein Parent article: Samba beats Windows (vnunet)
I'm assuming that you are referring to the Mindcraft tests of 1999. These are now too old to be of much interest as both Windows and Linux have moved on. For example, the Mindcraft tests used the Linux 2.2 kernel. Let's look at the world through the eyes of an IT manager. It's Windows' movement which is of interest to IT managers as it leads to a strategic headache. Software support for their Windows NT 4.0 file servers is coming to an end. The choices are to upgrade to Windows Server 2003, which is expensive and to operate well requires implementing Active Directory; or to cross-grade to Linux, which can be cheap and which does not require a change to authentication mechanisms. Samba's performance is a tactical consideration informing the strategic choice. The important point for the IT manager is that Samba does not perform poorly, no matter who's benchmark you believe. So the capacity planning numbers don't change too much between Windows NT and Samba. The capacity planning numbers for Windows 2003 Server are different. Going with Windows 2003 Server implies a hardware upgrade for most sites. So in going with Samba on Linux IT managers gain a further choice: cross-grade to Samba on Linux and retain the same hardware; or cross-grade to Samba on Linux on new hardware and do some server consolidation. The IT Week performance figures indicate that Samba's performance is >4x Windows 2003 Server. A well-choosen hardware upgrade could replace ten or more existing file servers. Unlike a Windows-based server consolidation those existing servers need not be trashed, they can run Linux and do less intensive tasks such as print serving, DNS and DHCP.
(Log in to post comments)
Samba beats Windows (vnunet) Posted Oct 14, 2003 13:52 UTC (Tue) by erat (guest, #21) [Link] The choices are to upgrade to Windows Server 2003, which is expensive and to operate well requires implementing Active Directory; or to cross-grade to Linux, which can be cheap and which does not require a change to authentication mechanisms.You hit on a subject (and all too quickly brushed past it) that I'm sure will tint IT folks' evaluations of WS2K3 and Linux/Samba: authentication, or more accurately, management of identity data. There was a time when machines running NT did little more than serve files, share printers, and perhaps run web servers (the latter still blows my mind. Why would anyone do such a thing??). Doing side-by-side comparisons of Windows servers and Linux servers was easier because the functionality expected of each was sort of limited. However, with identity management, evaluations become a bit more complicated. I've used WS2K3 and have done a fair amount of work with Active Directory (along with the cross-domain and cross-forest goofiness that goes along with it). As much as I hate to say it, I think it's a decent system. Setting up AD is fairly straightforward. And with apps like Vintela Authentication or with "experimental" configurations of LDAP/DNS/Samba/pam_smb you should be able to use identity data from AD with Linux. I won't get into an MS sales pitch because I'm sure they don't need/deserve the advertising, but I did want to point out that the identity management stuff in WS2K3 may actually be a selling point, not a hinderance. Onward... The new version of Samba has some capabilities of dealing with identity management (winbind?), and I believe it works with AD. I haven't looked into this; I'm merely parroting information that I heard elsewhere. A truly fair comparison between WS2K3 and Linux/Samba would need to include a comparison of how identity management works with AD and winbind, or even how Linux/Samba can be used to completely replace AD. As for speed... Compare how Linux/Samba stacks up against a WAN with WS2K3 servers that utilize cross-forest trusts (including identity firewalls), global catalog sync'ing across the WAN, etc. I'm not saying one will outshine the other because I haven't done any such benchmarking. I do think that kind of comparison is more valuable than one that simply places Linux/Samba on top just because it does a few things quickly.
|
|
||||||||||||