List:General Discussion« Previous MessageNext Message »
From:Waynn Lue Date:April 29 2008 10:26pm
Subject:Re: UPDATEs against one db affecting others
View as plain text  
I'll do that, thanks.  (Sorry for the long response time, I was in
Dublin this past week...).

On Mon, Apr 21, 2008 at 3:16 PM, Wm Mussatto <mussatto@stripped> wrote:
>
> On Mon, April 21, 2008 07:28, Waynn Lue wrote:
>  > Is there any way to prevent UPDATEs on one database on one mysql
>  > instance from affecting SELECTs on other databases in the same
>  > instance?  I'm noticing a whole bunch of backed up connections on
>  > other databases when I run massive UPDATEs on one.
>  >
>  > Thanks!
>  >
>  Are there any I/O or CPU load issues?
>  If you don't have any stored procedures that work between them, I'd check
>  server level limits.  MySQL is supposed to be multi-threaded to avoid just
>  this sort of problem, but if your disk and/or CPU are maxed out (or for
>  that matter you are out of memory) the whole system may be tied up.
>
>  Just my thoughts <warning its a Monday here>.
>
>  ------
>  William R. Mussatto
>  Systems Engineer
>  http://www.csz.com
>  909-920-9154
>
>
>  --
>
> MySQL General Mailing List
>  For list archives: http://lists.mysql.com/mysql
>  To unsubscribe:    http://lists.mysql.com/mysql?unsub=1
>
>
Thread
UPDATEs against one db affecting othersWaynn Lue21 Apr
  • Re: UPDATEs against one db affecting othersWm Mussatto22 Apr
    • Re: UPDATEs against one db affecting othersWaynn Lue30 Apr