On Tue, Oct 30, 2001 at 10:50:50AM -0500, C. Williams wrote:
>
> Sorry, semantic miscommunication. It's a heavily used table and the
> performance of other queries done during the mass deletion slows,
> which is a problem since this is a near-realtime system where delays
> in queries cause performance issues in other dependent modules.
Ah, okay.
A couple ideas:
(1) Try running smaller batches of deletes.
(2) Add a 'deleted' ENUM('N','Y') column to the table. Mark records
deleted but only run the delete processing when traffic is less
demandinng.
(3) See if you can safely increase the size of InnoDB's buffer
pool to help performance.
Jeremy
--
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936
MySQL 3.23.41-max: up 55 days, processed 1,220,547,898 queries (256/sec. avg)
---------------------------------------------------------------------
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
