How does Samba compare with NetWare in file and print serving?

How does Samba compare with NetWare in file and print serving?

How does Samba compare with NetWare in terms of efficiency in its file and print serving?

    Requires Free Membership to View

    Login

    When you register, my team of editors will also send you resources covering Linux administration and management; integration and interoperability between Linux, Windows and Unix; securing Linux and mixed-platform environments; and migrating to Linux.

    Cathleen A. Gagne, Senior Editorial Director

    By submitting your registration information to SearchEnterpriseLinux.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchEnterpriseLinux.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Another tough question to which the only answer I can give is: That depends!

You see, in terms of raw file serving there is mixed feedback about comparative efficiency. Some sites have claimed that Samba is faster, others that there is not much difference on the same hardware. No recent benchmarks are available to prove this one way or the other.

So far as file system intrinsics are concerned, NetWare has a file system that is far richer in terms of file attributes stored than a Unix file system. Samba is limited by the intrinsic capabilities of the native file system it sits on top of.

One area where Samba pays a very high price is in the handling of 8.3 file names. Samba implements a method of file name mangling to dynamically create 8.3 file names. Additionally, Unix/Linux file systems are case preserving and case sensitive -- under a Unix environment Samba has to implement case insentive file name handling itself. This is user-space CPU intensive. NetWare is built for this type of file name handling, does this in kernel space, and thus with lower overhead.

So in real world benchmarks I would expect (on the same hardware) that in raw file serving Samba may outperform NetWare, but on filename resolution NetWare would run rings around Samba.

This was first published in May 2003