> > Key phrases: "if asked to do so" and "data it collects". GIGO. > > I believe you have not even tried...
Read what I said, not what you think I said, Rob. PerfKit collects what it's told to collect when asked to do so. If you didn't tell it to do it, it's not going to guess, and that's the data you have to work with. > Even when you charge people just on the CPU usage per virtual machine, > you can wait for the moment they come back and want you to justify the > charges since they "have not been using that much" So even for > something that trivial, you want to be able to come up with process > data. And guess what happens when you process data does not match the > VM data - pretty weak case to convince them. While ordinarily I'd agree, there are situations where good enough is good enough. Is this universal? No. Are there situations where it's sufficient? Yes. Can you produce something that is satisfactory to a customer using PerfKit? Yes. Are there alternatives? Yes. I guess we'll have to agree to disagree. PerfKit gives me data that I find useful and that I can correlate the data I get acceptably well. YMMV. -- db ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
