Even if you break it into smaller blocks, you still need to transfer the data to the controller, then the controller has to employ overhead to break up the block, create the parity information, determine the location for each block, etc.
With RAID-1 the controller can just write through and duplicate the operation "as is" on the second bank. http://www.acnc.com/04_01_05.html vs. http://www.acnc.com/04_01_01.html RAID-1 has less overhead during writing. Since the spool folder probably has a 1:1 read/write ratio - it is sensitive to "write" performance. RAID-5 works well for write once - read many times applications, such as file and database servers. Best Regards Andy Schmidt Phone: +1 201 934-3414 x20 (Business) Fax: +1 201 934-9206 -----Original Message----- From: Goran Jovanovic Sent: Wednesday, March 16, 2005 11:26 AM I guess this is going against what I think should be happening. In a RAID 5 array the write to the drives is broken into many smaller writes along with the data protection/CRC info and then those writes are written to different drives. It seems to me that it should be faster to do a bunch of small writes rather than 1 big write. This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
