john.marco
Registered
<p>After f0rking around with MacOS X for the last week I've found that the UFS* filesystem seems to have VERY poor performance on my iMac 500 SE.
<p>(UFS = Unix File System, the 'other' type allowed under the Disk Setup Util during install)
<p>Under PB:
<p>I installed with UFS as the 'install-to' destination.
<p>1. Could never get Classic to run. (Turned out the trick was to copy the 'Classic' folder to the HFS+ partition on which I had 9.1, but anyhow..)
<p>2. File system performance was DOG SLOW! I just chalked this up to being a beta and figured there was a lot of debug code in place, but the disk sure was thrashing around a lot for even minor things.
<p>Under 10.0.0
<p>I wiped my entire HD clean and repartitioned with
everything on one great big 30GB HFS+ partition.
Also immediately installed the DevTools because I'm a developer.
<p>1. This was MUCH FASTER than PB! Almost as fast as 9.1.
<p>2. Noticed that file names are not case sensitive in HFS+. This offends my puritanical Unix hacker sensibilities, so I decide to reformat and try out UFS. (I do most of my work with Unix and java stuff)
<p>3. After reformatting with UFS, it was dog slow again. Even slower than PB. Started to consider that UFS sucks when it comes to performance.
<p>Under 10.0.1
<p>I added the 4L5 patch with no improvement in speed. This is not surprising since I use DevTools, which does the same prebinding optim. as 4L5.
<p>Finally I got tired of the slowness and reformatted my drive:
<p>Partition 1: 10GB HFS+
<p>Partition 2: 18GB UFS
<p>I then installed (fresh) MacOS 9.1 on P1, then installed OSX on P1 along with 9.1. P2 just gets mounted under /Volumes/Unix and I symlink my 'work' directories to it for doing Unix hacking that likes old style case sensitive filesystem semantics. Also, things like tar can get the resource fork on UFS, since it's hacked as ._<foo> and is thus visible, unlike with HFS+.
<p>This configuration is MUCH FASTER! Just like when I first installed on HFS+ only! With UFS, my system would take twice as long to boot as my P2/450 Peecee running Win2k Pro, and that's saying a LOT! Now it boots in half the time that Win2K does. That's roughly a 4x speedup! Logins used to take about a minute and now they come up in 5-10 seconds or so. MUCH BETTER!
<p>The moral of this story?
<p>Don't use a UFS filesystem as your install destination. It's too slow! Use HFS+ as the system/install partition, and maybe have a second UFS partition for doing Unix stuff if you're into that. If you don't give a hoot about Unix, you probably just want to use HFS+ for everything anyhow.
<p>Another advantage of installing on HFS+..
<p>Classic just works. You don't have to copy the Classic folder from (I think) 'Applications' to a folder on the HFS+ partition, since it's already ON the HFS+ part.
<p>To get an idea of the performance difference I'm seeing, I saw probably a 5x improvement in perceived speed by switching back to HFS+. YMMV of course. I'm probably also suffering because of a crappy 5400RPM disk, unless the iMac500's come with something faster, so every bit of disk performance improvement helps me.
<p>The question is, Why is UFS so slow? I don't know for sure, but I suspect it could be a number of things.
<p>1. The resource fork hack, requiring two separate inode (basically file) lookups for each file. The buffer cache should speed this up, though.
<p>2. Maybe UFS is doing anal-retentive synchronous write-throughs on writes.
<p>3. Maybe UFS is misconfigured and is not using the buffer cache at all?!?! This would be nasty and would explain the MS-DOS-like disk performance I'm seeing.
<p>4. UFS is decades-old crap anyhow. Give me a journalling file system any day. UFS performance is not exactly stellar under FreeBSD on my peecee.
<p>5. My disk I/O hardware is crap. They don't make iMacs with RAID5 and 15000 RPM disks, and for under $2K. hehe.
<p>I'll bet a good number of folks who are reporting no improvements with either DevToosl install or 4L5/4L7 are running UFS as their main 'install destination' for
Mac OS X.
<p>I dunno. I hope this helps.
<p>(UFS = Unix File System, the 'other' type allowed under the Disk Setup Util during install)
<p>Under PB:
<p>I installed with UFS as the 'install-to' destination.
<p>1. Could never get Classic to run. (Turned out the trick was to copy the 'Classic' folder to the HFS+ partition on which I had 9.1, but anyhow..)
<p>2. File system performance was DOG SLOW! I just chalked this up to being a beta and figured there was a lot of debug code in place, but the disk sure was thrashing around a lot for even minor things.
<p>Under 10.0.0
<p>I wiped my entire HD clean and repartitioned with
everything on one great big 30GB HFS+ partition.
Also immediately installed the DevTools because I'm a developer.
<p>1. This was MUCH FASTER than PB! Almost as fast as 9.1.
<p>2. Noticed that file names are not case sensitive in HFS+. This offends my puritanical Unix hacker sensibilities, so I decide to reformat and try out UFS. (I do most of my work with Unix and java stuff)
<p>3. After reformatting with UFS, it was dog slow again. Even slower than PB. Started to consider that UFS sucks when it comes to performance.
<p>Under 10.0.1
<p>I added the 4L5 patch with no improvement in speed. This is not surprising since I use DevTools, which does the same prebinding optim. as 4L5.
<p>Finally I got tired of the slowness and reformatted my drive:
<p>Partition 1: 10GB HFS+
<p>Partition 2: 18GB UFS
<p>I then installed (fresh) MacOS 9.1 on P1, then installed OSX on P1 along with 9.1. P2 just gets mounted under /Volumes/Unix and I symlink my 'work' directories to it for doing Unix hacking that likes old style case sensitive filesystem semantics. Also, things like tar can get the resource fork on UFS, since it's hacked as ._<foo> and is thus visible, unlike with HFS+.
<p>This configuration is MUCH FASTER! Just like when I first installed on HFS+ only! With UFS, my system would take twice as long to boot as my P2/450 Peecee running Win2k Pro, and that's saying a LOT! Now it boots in half the time that Win2K does. That's roughly a 4x speedup! Logins used to take about a minute and now they come up in 5-10 seconds or so. MUCH BETTER!
<p>The moral of this story?
<p>Don't use a UFS filesystem as your install destination. It's too slow! Use HFS+ as the system/install partition, and maybe have a second UFS partition for doing Unix stuff if you're into that. If you don't give a hoot about Unix, you probably just want to use HFS+ for everything anyhow.
<p>Another advantage of installing on HFS+..
<p>Classic just works. You don't have to copy the Classic folder from (I think) 'Applications' to a folder on the HFS+ partition, since it's already ON the HFS+ part.
<p>To get an idea of the performance difference I'm seeing, I saw probably a 5x improvement in perceived speed by switching back to HFS+. YMMV of course. I'm probably also suffering because of a crappy 5400RPM disk, unless the iMac500's come with something faster, so every bit of disk performance improvement helps me.
<p>The question is, Why is UFS so slow? I don't know for sure, but I suspect it could be a number of things.
<p>1. The resource fork hack, requiring two separate inode (basically file) lookups for each file. The buffer cache should speed this up, though.
<p>2. Maybe UFS is doing anal-retentive synchronous write-throughs on writes.
<p>3. Maybe UFS is misconfigured and is not using the buffer cache at all?!?! This would be nasty and would explain the MS-DOS-like disk performance I'm seeing.
<p>4. UFS is decades-old crap anyhow. Give me a journalling file system any day. UFS performance is not exactly stellar under FreeBSD on my peecee.
<p>5. My disk I/O hardware is crap. They don't make iMacs with RAID5 and 15000 RPM disks, and for under $2K. hehe.
<p>I'll bet a good number of folks who are reporting no improvements with either DevToosl install or 4L5/4L7 are running UFS as their main 'install destination' for
Mac OS X.
<p>I dunno. I hope this helps.