If possible, use web server logging to get the timings. As I explained in my previous essay, this is not at all simple or easy.
If you run a benchmark more than once, be sure to reboot the system between runs. Regards, Jerry Schwartz Global Information Incorporated 195 Farmington Ave. Farmington, CT 06032 860.674.8796 / FAX: 860.674.8341 E-mail: [email protected] Web site: www.the-infoshop.com >-----Original Message----- >From: Shawn Green (MySQL) [mailto:[email protected]] >Sent: Friday, September 10, 2010 7:56 AM >To: Johan De Meersman >Cc: Nunzio Daveri; [email protected]; [email protected] >Subject: Re: Replaying the mysqld.log file from production onto QA??? > >Hello Johan, > >On 9/10/2010 7:47 AM, Johan De Meersman wrote: >> On Thu, Sep 9, 2010 at 4:12 PM, Nunzio Daveri >> <[email protected]>wrote: >> >>> So.. I am trying to mimic replaying production like queries so joins, temp >>> tables etc... are stuff I am trying to test as well. Just doing a dump >>> and >>> import is no more than export and importing, I also want to test selects, >>> updates :-) Thanks for replying :-) >>> >> >> >> Then you'll have to first activate full logging on your production server. >> This may take quite some diskpace, and IOs, so keep the logfiles on >> separate >> spindles. >> >> Extracting the queries from the log shouldn't be all that hard; but there's >> too little timing information in there to do a time-true replay - and I >> don't know of any app that does that, either. >> > >He already did! Those are the logs he needs to replay. He has the logs >already but needs tools to extract the commands and repeat them as a >load test. > >Do you have any techniques you can share? > >-- >Shawn Green >MySQL Principal Technical Support Engineer >Oracle USA, Inc. >Office: Blountville, TN > >-- >MySQL General Mailing List >For list archives: http://lists.mysql.com/mysql >To unsubscribe: http://lists.mysql.com/[email protected] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[email protected]
