overhead in memory tables

------=_NextPart_000_0C8E_01CBCCF8.AA92E360
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Hello.

We have a table using the memory engine and we notice in PMA that the =
overhead continues grow over time. Normally we'd optimize with such an =
issue but that is not applicable to memory based tables. So... does =
this pose a problem for long term use of the table? If so, is there a =
recommended way to deal with it other than switch to a new table engine? =
=20

We are not experiencing any problems at this time, we are just trying to =
be proactive about it.

Mysql version is 5.5.9 + memcached

Thanks.


------=_NextPart_000_0C8E_01CBCCF8.AA92E360--

Re: overhead in memory tables

--0015174be90cfdb78d049c53a609
Content-Type: text/plain; charset=ISO-8859-1

What particular overhead is growing ? :-)

On Tue, Feb 15, 2011 at 10:11 AM, Geoff Galitz wrote:

>
> Hello.
>
> We have a table using the memory engine and we notice in PMA that the
> overhead continues grow over time. Normally we'd optimize with such an
> issue but that is not applicable to memory based tables. So... does this
> pose a problem for long term use of the table? If so, is there a
> recommended way to deal with it other than switch to a new table engine?
>
> We are not experiencing any problems at this time, we are just trying to be
> proactive about it.
>
> Mysql version is 5.5.9 + memcached
>
> Thanks.
>
>


--
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel

--0015174be90cfdb78d049c53a609--