From: Scott Pham (spham@incellico.com)
Date: Wed Mar 19 2003 - 12:25:19 EST
Fellow Sun Managers,
My colleagues and I are debating on what type of disk layout we should use
and if it should be a cooked or a raw fs. I know there are a lot of threads
out there for this exact debate. My current configuration is V880, with 2 T3
workgroup arrays. I understand that going with a raw fs has a high
administrative cost, but what I don't currently understand is; the
administrative cost for raw fs, is the high administrative cost during the
initial setup of the database or the lifetime of the database? I would like to
hear agruments for both sides. Why would someone pick raw vs cooked. One thing
is for sure. We don't know if the io is a bottleneck yet. During the build of
the database, it will have alot of writes. Once the db is built. It will be
used mostly for reads. The db itself will be around 400-900gb. I know vertias
quick i/o is a good addon, but I'm afraid it's not in the current budget.
Thanks in advance.
"They that can give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:26:01 EDT