Can I have 30GB of Innodb Index on a 16GB 2CPU quad core server?

--0-1984165437-1280428168=:95949
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi All, I was running slamdb against one of our QA boxes and noticed that t=
he =0Ainnodb database is 190Gb in size BUT the worrying issue is that the i=
ndexes are =0A30GB in size!!!=A0 When I hit this server hard, it tanks on m=
emory but still =0Aperforms, slower of course ;-)=A0 Any suggestions on wha=
t I should do?=A0 I am =0Athinking of doing one of these: 1. Remove al=
l queries, run for a few days, look at the slow query logs and then =0Afind=
those queries that really need them and index those specificially for =0Ap=
erformance.=0A2. Split the single server into two servers both with 16 gb a=
nd 2 quad core =0Acpu's. One master the other a slave.=0A3. Just add anothe=
r 16gb (32GB total) and that should take care of the indexing =0Aissue.=0A=
=0AAnyone had this problem before??? Oh this is a single box, 100% mys=
ql only and it talks to 3 front end iPlanet web =0Aservers that hit it with=
a few hundread queries per second. Thanks... Nunzio =0A =

--0-1984165437-1280428168=:95949--