We did two things that significantly improved our insert performance. The first was putting a transaction around the entire insert process and committing the transaction at the end (this has been documented in this list several times before). The second was to perform the inserts in "bulk" mode - i.e., - we store the rows in an array and execute the insert as a single statement (usually in "chunks" of 250,500, or more). This is performed through the ODBC API calls and some internally developed libraries, so I don't know if this method is appropriate for your application, but it made a world of difference in ours.

Regards,
Mark

Javier Gostling wrote:

Hello,
I have been measuring performance of SapDB for a forums application and
have a problem with performance of inserts. Tests have shown that the
system can show more than enough messages per second to sustain the
activity in the forums, but when posting, performance drops severely.

Now, my tests were done first against a development database with about
150.000 messages in the messages table, and post performance is quite
adequate, but when I load the data from the current production database,
then performance starts suffering badly. The production database has
around 1.6 million messages stored (old messages are archived to prevent
overgrowth of the table).

This table has several indexes, so I think that the problem might be
sapdb having to insert the data into the table and update the indexes as
well. Has anyone seen this behaviour in data sets of this size? Any
suggestions on how to improve performance? Any additional info you might
need to shed some light?

Thanks,




--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to