pretty big change performance-wise for the better or worse? what is a potential negative outcome of dirty reads?
Thanks for all this info. ~Chad On 8/7/07, Ben Reece <[EMAIL PROTECTED]> wrote: > > > Wade Preston Shearer wrote: > >> The other engines have options to allow dirty reads, but MyISAM > >> doesn't, unless use the MySQL handlers instead of queries, but it's a > >> lot more work. > > > > What would you recommend as an alternative? What are some best > > practices or common solutions? > > > The InnoDB engine allows dirty reads, but it can be a pretty big change > performance-wise, depending on how you're using it. > > Though in the specified example, if a delete like that is taking a long > time, either a) the row data is very large, b) there are an insane > number of rows, or c) the server's pretty slow. Even deleting 1/2 of a > million rows, it should only take a few seconds, and can be run once a > day during non-peak times. > > Ben > > _______________________________________________ > > UPHPU mailing list > [email protected] > http://uphpu.org/mailman/listinfo/uphpu > IRC: #uphpu on irc.freenode.net > -- /--------------------------/ Chad Sollis [EMAIL PROTECTED] 801.792.7651 _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
