Hello Denis,
Tuesday, July 10, 2001, 12:51:40 PM, you wrote:
If I'm not mistaken the problem is - conflicting transactions which
you have here. I'm really not shure INNODB dead lock detection is
quite fine graned. Also it's shurely may roll back more long running
transaction. But anyway you should be ableto handle this.
DP> Hi all,
DP> I begin to validate MySQL with InnoDB on our platform. I use a DBI perl
DP> test which manages a data pool reflecting exactly the rows stored in DB.
DP> This test internally builds some new data to insert and chooses rows to
DP> delete and update (the tables are chosen randomly). Then all these
DP> operations are executed in one transaction. If it fails, a rollback is
DP> executed in DB and in client memory. Client also check that all data in
DP> its pool are in the DB. That's my test...
DP> It works very well with one client, but with two... things become
DP> harder! clients received many 'Table handler error 1000000' and slow
DP> down terrifically.
DP> I try the same test with 3 clients on MyISAM tables and there is no
DP> noticeable problems.
DP> I have reduced number of queries per transaction. I have changed
DP> innodb_unix_file_flush_method to O_DSYNC. I have increased buffer pool
DP> size and log buffer size but I noticed onlky small improvements. I'm
DP> sure I forgot something, but I don't see what ! does somebody know ??
DP> Denis
--
Best regards,
Peter mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
