| OS/2 Filesystem Shootout! |
|
|
|
Posted by Administrator - Tuesday, 14 May 2002
Because I'm a curious person, I wanted to know which one of these IFSs is the best. The following paragraphs are an attempt to find an answer to this question. Perhaps not too surprisingly, there is no clear answer... but read on. The days of DOS when you could choose any filesystem as long as it was FAT are long gone. Since the introduction of OS/2 Warp Server for e-Business, OS/2 and eCS users can choose between three IBM supplied filesystems (FAT, HPFS, JFS) and four file system drivers - for HPFS there are two possibilities, "regular" HPFS and HPFS386, although the latter is only available in server versions and at considerable extra cost. I don't even count the variety of third-party IFSs - most of them have very specific purposes and are not suitable as generic filesystem drivers due to poor performance, lack of features or special intended uses. Because I'm a curious person, I wanted to know which one of these IFSs is the best. The following paragraphs are an attempt to find an answer to this question. Perhaps not too surprisingly, there is no clear answer... but read on. If we want to choose the "best" IFS, we need to be able to tell if one IFS is better than another. I decided to compare the filesystems based on performance and features. Features are rather difficult to express in numbers- which leaves us with performance, and to compare the filesystem performance it is necessary to run benchmarks. Unlike some hot benchmarking "pros" I'm not going to pretend that my benchmarks are universally applicable or necessarily even important. Draw your own conclusions from the numbers - and at your own risk. If you want to be really sure, roll your own benchmarks which model how you use your computer. First I will describe the hardware used for benchmarks. It is a 600 MHz Pentium III with 256MB RAM and Maxtor 40GB 7200RPM EIDE disk. I did not run the tests on this disk however - for that I used a Fujitsu Ultra-160 18.2GB 7200RPM SCSI disk attached to a venerable Adaptec 2940UW PCI SCSI host controller. This setup allowed me to create one relatively small 1GB volume and reformat it with various filesystem. That ensured that all tests were run on a clean, unfragmented volume and that there was no skew introduced by different speeds of different parts of the disk. With this setup I am reasonably certain that it was only the IFSs that made the difference between test results and no other factors. In retrospect, using the fast SCSI drive for benchmarking wasn't a very good idea for a simple reason: a fast drive tends to equalize the filesystem differences in performance. Look at it this way - if the disk was infinitely fast, there should be no differences in filesystem performance. The slower the disk, the more important the IFS efficiency becomes. Still, even with the fast drive there were clearly discernible trends in filesystem performance. For both HPFS386 and JFS I used 32MB caches with default settings for lazy write timeouts etc. For plain HPFS I used the maximum 2MB cache and for FAT the maximum 14MB cache. The base sytem was eCS GA with HPFS386.IFS from WSeB GA and JFS.IFS from October 16, 2001. At first I intended to run "classic" benchmarks from SysBench but then decided against it for two important reasons:
![]() The above table makes several points very clear:
These differences are not suprising given these filesystems' very different history: HPFS386 was reportedly written by Gordon Letwin, the father of HPFS, in late 1980's. JFS was developed for IBM's variant of Unix, AIX (probably in early 1990s). HPFS386 is hand optimized 386 assembly code, JFS is written in C - but the above numbers show that there's more to performance than tight loops. If we can't decide which IFS is better on performance, we can try to base the decision on features. As I hinted above, this is not easy because features are impossible to quantify. Only individual user with specific needs can decide which feature set suits him or her best. A detailed description of the respective filesystems' feature sets can be found elsewhere so I'll just summarize the points that I find most important:
My personal choice is JFS for one simple reason: HPFS386 is a dead end. It is partially owned by Microsoft and no one can seriously expect any new development to be done on it. That was the reason why IBM decided to include JFS in WSeB after all. JFS on the other hand is available in source code and JFS support was added to Linux. In other words - nobody can take JFS away which is more than can be said for HPFS386. Conclusion I'm not going to make a choice for anyone else. You decide what's best for you. I attempted to present some interesting (and perhaps even unexpected) data here but you have'll to draw your own conclusions. I won't pretend I know what's best for you. Maybe you don't either, but that's another matter. Michal Necasek (0) Comments |
| < Prev | Next > |
|---|
Main Menu
| Home |
| Annual Awards |
| Bounty System |
| Hosted pages |
| OS2 Forums |
| OS2 Petition |
| OS2 Library |
| OS2 Wiki |
| Sponsors |
| News Sections |
| FAQs |
User login
PayPal Donations
Copyright 2000-2008 OS2 World.Com






