|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Waynn Lue (waynnlue
gmail.com)
Date: Tue Apr 29 2008 - 17:26:15 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
csz.com> 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=waynnlue
gmail.com
>
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]