From: Johan De Meersman
Date: April 22 2010 7:20am
Subject: Re: More CPU or More RAM?
List-Archive: http://lists.mysql.com/mysql/221369
Message-Id: <n2haaba5c101004220020ra17d91abld9233bbe704dc3@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=001485eba2cc597d8e0484ce26ca

--001485eba2cc597d8e0484ce26ca
Content-Type: multipart/alternative; boundary=001485eba2cc597d880484ce26c8

--001485eba2cc597d880484ce26c8
Content-Type: text/plain; charset=ISO-8859-1

Also, have some munin plugins. There are the ones I add to the ones in a
standard munin distribution, and give plenty of info.

Only the mysql_ one is actually mine, I got the rest off muninexchange.
Guess I should incorporate their functionality into mine sometime.

A good look at the data that comes out of these (and an understanding of how
MySQL works, of course) will tell you what's up, what's happened and where
to tune.

On Thu, Apr 22, 2010 at 9:12 AM, Johan De Meersman <vegivamp@stripped>wrote:

>
> On Wed, Apr 21, 2010 at 4:52 PM, shamubro@stripped <shamubro@stripped>wrote:
>
>> replacement etc, but that costs me too much if I can use hardware to solve
>> the same problem. and Yes I know I will run to same problem again when the
>>
>
> It may be that you can't actually solve it with more hardware. The version
> of drupal we were using (we've built a highly customised one by now) had the
> annoying tendency to explicitly lock tables, even when not strictly
> necessary. A lock is a lock, regardless of how much hardware you throw
> against it.
>
> --
> Bier met grenadyn
> Is als mosterd by den wyn
> Sy die't drinkt, is eene kwezel
> Hy die't drinkt, is ras een ezel
>



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

--001485eba2cc597d880484ce26c8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Also, have some munin plugins. There are the ones I add to the ones in a st=
andard munin distribution, and give plenty of info.<br><br>Only the mysql_ =
one is actually mine, I got the rest off muninexchange. Guess I should inco=
rporate their functionality into mine sometime.<br>
<br>A good look at the data that comes out of these (and an understanding o=
f how MySQL works, of course) will tell you what&#39;s up, what&#39;s happe=
ned and where to tune.<br><br><div class=3D"gmail_quote">On Thu, Apr 22, 20=
10 at 9:12 AM, Johan De Meersman <span dir=3D"ltr">&lt;<a href=3D"mailto:ve=
givamp@stripped">vegivamp@stripped</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><div class=3D=
"gmail_quote"><div class=3D"im">On Wed, Apr 21, 2010 at 4:52 PM, <a href=3D=
"mailto:shamubro@stripped" target=3D"_blank">shamubro@stripped</a> <span =
dir=3D"ltr">&lt;<a href=3D"mailto:shamubro@stripped" target=3D"_blank">sha=
mubro@stripped</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
replacement etc, but that costs me too much if I can use hardware to solve<=
br>
the same problem. and Yes I know I will run to same problem again when the<=
br></blockquote></div><div><br>It may be that you can&#39;t actually solve =
it with more hardware. The version of drupal we were using (we&#39;ve built=
 a highly customised one by now) had the annoying tendency to explicitly lo=
ck tables, even when not strictly necessary. A lock is a lock, regardless o=
f how much hardware you throw against it. <br>

</div></div><br>-- <br><div><div></div><div class=3D"h5">Bier met grenadyn<=
br>Is als mosterd by den wyn<br>Sy die&#39;t drinkt, is eene kwezel<br>Hy d=
ie&#39;t drinkt, is ras een ezel<br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Bier met gr=
enadyn<br>Is als mosterd by den wyn<br>Sy die&#39;t drinkt, is eene kwezel<=
br>Hy die&#39;t drinkt, is ras een ezel<br>

--001485eba2cc597d880484ce26c8--
--001485eba2cc597d8e0484ce26ca--