>> >> OLTP >> > > Isn't this the case of an application (e.g. vdbench, filebench) having > slightly differing behavior and the underlying storage being a better > match to one or the other? I am not surprised by this. If you were > to say the workload was something like sequential read, then it > would be a surprise. >
This is exactly the point of model-based workload synthesis! Since the oltp workload is sensitive to things like the latency of redo-log writes, it can and will intentionally perform different to a simple random I/O workload. It would be interesting to see what parts of the model showed wait-times or longer latencies -- do you have the output? Thanks, Richard. _______________________________________________ perf-discuss mailing list perf-discuss@opensolaris.org
