>>>>> "Adam" == Adam Levin <[email protected]> writes:
Adam> As a general rule, sequential streams (sustained read/write) are the bread and Adam> butter of spinning rust. SSD's eat random seeks for breakfast. The trick Adam> here, though, is whether the it's worth the extra money to get SSD over the 15k Adam> with only a gigabit ethernet connection. I'm inclined to say that if your Adam> workload is seriously random, you'd be better off with SSD, because random Adam> workloads won't get close to those speeds anyway. The one caveat here is if Adam> it's the same data over and over again, then a simple cache in front of 15k Adam> would probably outperform that. It's a delicate ballet of criteria. Either Adam> the SSD or 15k will crush the 7200's performance, that's for sure. SSD is also Adam> easier on power consumption and should, in theory, be more reliable (assuming Adam> you get good quality drives). Adam> That didn't help at all, did it? Sigh... Heh! My reply didn't help either.... But the question really didn't give enough information on the problem space and what he's trying to solve. It's probably not a DB or any type, since runnign one of them over a NAS would seriously suck. It might be a NNTP server, or mail server with lots of small(ish) random data. It could be a data logger and stats summarizer tool, which adds data and then generates reports. It could be a home directory for students doing lots of random compiles, edits and debugging sessions across large source code trees. Lots of ideas here... and honestly, trying to speed up a Drobo isn't the path I'd take. I'd use it for storing large sequential data sets, and bring the storage (SSD, or SSD/SATA cache type setup) local to the system to improve performance. John _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
