Ted. Please be patient. I didn't say I won't post the data. I am not doing the test myself. My team does. I saw iostat result when they did the test.
I cannot cut-and-paste what I don't have. I cannot force them to come in on weekends to do the testing. and let me add. There is no magic in iostat. They are hard data came from device driver, and calculated from utilization law ;) Thanks. Chang 2011. 4. 17., 오전 5:43, Ted Dunning 작성: > That isn't the issue. > > The issue is that there is something here that is a mystery. You aren't > seeing the answer. If you could, you would have seen it already and > wouldn't have a question to ask. If you want somebody else to see the > answer, you need to show them the raw data and not just tell them your > interpretation of the situation. If you don't want to show the raw data > because it is embarrassing to admit that you might not be seeing something, > then you should just not ask the question. > > It doesn't matter how much you know or how well you can interpret things > normally. You are adding your interpretation to the raw data and there is > something in this interpretation or your description of the situation that > is faulty. The only way to get past that is to allow others to interpret > the raw data. > > This happens to everybody at some point. New eyes see new things and > sometimes that is just what is needed. > > 2011/4/15 Chang Song <tru64...@me.com> > >> But please note that I used to be a kernel filesystem engineer, and I know >> how to read iostat ;) >>
