Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Disk Journaling' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Disk Journaling
Authored by: Bioinformatics on Apr 07, '03 05:55:41PM

I'm not an expert on this by any stretch of the imagination, but my impression is that journalled filesystems are shouldn't be that hard on system. They - in principle - should only tie up some RAM (for the tables they use), and soak up a little background CPU to write contents back to disk when CPU is available. There should be little effect on reading performance. How go the system is at balancing tasks might come in play, too. But none of this should be a bg hit on a well-configured system. There will be a little overhead - there is another system service running - but it shouldn't be dramatic.



[ Reply to This | # ]
Disk Journaling
Authored by: DanFrakes on Apr 07, '03 07:03:13PM

According to Apple, the performance hit is significant. OS X Server (which offers journaling as a standard feature) has been tweaked to reduce this hit; however, OS X standard hasn't. I have a feeling that OS X standard will eventually offer journaling as a standard feature, and by that time OS X will have been tweaked to minimize this performance hit.

That being said, the truth is that journaling is really a server-level feature. It was developed for computers with very large volumes where (1) data integrity and (2) minimal downtime are of utmost importance. For the average user, you're better off keeping it disabled and simply backing up regularly, IMO. You'll get better performance, similar reliability, and more functionality (you'll be able to use fsck, Disk Warrior, and other disk utilities that can't be used on journaled systems without a bunch of caveats).



[ Reply to This | # ]
Disk Journaling
Authored by: DaveD on Apr 08, '03 11:24:06AM

I'm sorry, but I must say that I disagree. I have used journaling file systems on BeOS, Linux (ext3, reiserfs, etc), and the journaling has in no way slowed down the system, or caused any sort of hit in system performance. While I am not saying that Apple's has issues, or that the slowdown is something that will be worked out as things mature, I do know that journaling should not cause a performance hit <when properly implemented>.



[ Reply to This | # ]