I'm writing a program to do some informal benchmarking of insert and query performance using various MySQL storage engines using MySQL 5.1.x latest beta. I've got it up and running just fine using Lazarus and the MySQL components. It was a piece of cake.
My question is on what the best way is to do the inserts to get the truest picture of insert performance. Right now I'm basically constructing an insert statement string and using ExecSQL to do the insert. Is there another way (perhaps one a little more object-oriented) to do inserts other than just piecing together a huge "Insert into table t1 (a, b, c, d,) values ..."-style statement? If not, would I get better performance inserting multiple records with each statement I execute (insert into t1 values (1), (2), (3), ... etc.) or inserting one record per statement (insert into t1 values (1); insert into t1 values (2); etc.? Any tips you have would be appreciated. I just want to eliminate as much as possible any performance hits due to the overhead of the tools I'm using to do the benchmarking, thus getting a better picture of the performance of the database itself. Thanks, Seth Grover -- Seth Grover sethdgrover[at]gmail[dot]com http://grovers.us/seth I'm a driver, I'm a winner. Things are going to change, I can feel it. _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
