I would intentionally mix assuming I can still meet io rrequirements, this generally will help balance since they have seperate io signatures...sequential reads versus small block mixed io etc.

Fred Grieco fredgrieco@yahoo.com wrote:

What is the best practice for mixing (or not mixing) different I/O load types in an aggregate? Should I keep similar loads together, or "mix and match" the sets.

For instance, I am looking at placing a variety of different data sets on four aggregates. These data sets include sequential backups-to-disk, nfs and cifs file shares, and "QA-dev" luns. Should I keep all the backups on one aggregate, and all the file shares on another? What do you generally do? Are there situations that will adversely affect performance?

TIA, Fred

Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.