tag:blogger.com,1999:blog-34926058.post1350096440013044469..comments2020-11-05T19:55:50.110-08:00Comments on DSO Guy: What were those results again?Steve Harrishttp://www.blogger.com/profile/17342689039838434111noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-34926058.post-38203909290930332952007-07-30T14:15:00.000-07:002007-07-30T14:15:00.000-07:00Or better yet, log all the important data to analy...Or better yet, log all the important data to analyze later. Do it in a format that easy to import in spreadsheet and charting tools (csv,tab delimited etc.). Nmon does a very good job of giving very useful and rich set of data (cpu, network, disk .. you name it).<BR/><BR/>Cheers.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-34926058.post-63250402673499844172007-07-30T14:12:00.000-07:002007-07-30T14:12:00.000-07:00Or better yet, log all the important data to look ...Or better yet, log all the important data to look at later :)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-34926058.post-39987085522467705822007-07-19T18:56:00.000-07:002007-07-19T18:56:00.000-07:00This is simple but great advice that matches my ex...This is simple but great advice that matches my experience. I have actually gone so far as to write a script that wrapped each test run to automatically record date, time, copy key config files, tuning parameters, etc and stuff them in a directory somewhere. That has saved me more than once. It doesn't take very many tests before it's easy to get confused.Alex Millerhttps://www.blogger.com/profile/01929662536395624733noreply@blogger.com