|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Nico Sabbi (nicola.sabbi
poste.it)
Date: Tue Apr 28 2009 - 16:17:53 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Il giorno mar, 28/04/2009 alle 17.11 -0400, Baron Schwartz ha scritto:
> Hi,
>
> On Tue, Apr 28, 2009 at 1:04 PM, Rolando Edwards
> <redwards
logicworks.net> wrote:
> > Make sure the tables that the information_schema are not locked.
> >
> > This is because MyISAM tables, that are constantly being inserted into (Each insert, update, delete on a MyISAM table does a table lock), must update the TABLE_ROWS column in information_schema.tables to have the latest count.
>
> That's not how INFORMATION_SCHEMA works. Those aren't real tables.
>
> Behind the scenes it is just doing SHOW TABLE STATUS on each table and
> populating a temporary structure with the results.
>
> Nico, it is my opinion that I_S is not suitable for heavy production
> use :-) I have seen several cases of severe performance problems
> caused by it.
>
> Baron
after what I'm seeing I can't avoid to agree completely.
I also read of extremely serious DOS problems caused by this crazy (and
severely castrated) implementation of the I_S. How did it end up in
mainline?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]