tag:blogger.com,1999:blog-4420251135122552368.post3524521611507391257..comments2023-09-04T03:43:09.277-07:00Comments on ScaleAholic: What were those results again?Steve Harrishttp://www.blogger.com/profile/17342689039838434111noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-4420251135122552368.post-64148773700242822602007-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 Millerhttp://www.blogger.com/profile/01929662536395624733noreply@blogger.comtag:blogger.com,1999:blog-4420251135122552368.post-2684065314633849692007-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-4420251135122552368.post-10731982693150663772007-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.com