Slow disk access: 1.4m to do a select count over 23GB table.

--00c09f88d2036a8b38048b00b13e
Content-Type: text/plain; charset=ISO-8859-1

Hi, I'm using mysql 4.1.21, a legacy system. Next step to migrate it, but
for now, I need the community help.

I have a 23GB table, if I do a select count(over_an_index) from table it
uses 1.4minutes to read. The main issue is that this table is the main table
of a system and each query is taking too long to complete.

How can I optimize the access of the database?

any mysql variable I could use?
or how can I load the index into memory? I have 32GB of ram XD plenty to
useit into something more useful....


Thanks.

--00c09f88d2036a8b38048b00b13e--

Re: Slow disk access: 1.4m to do a select count over 23GB table.

On Fri, Jul 9, 2010 at 9:09 PM, Andr=E9s Tello wrote=
:
> Hi, I'm using mysql 4.1.21, a legacy system. Next step to migrate it, but
> for now, I need the community help.
>
> I have a 23GB table, if I do a select count(over_an_index) from table it
> uses 1.4minutes to read. The main issue is that this table is the main ta=
ble
> of a system and each query is taking too long to complete.

A table definition would be heplful here.

> How can I optimize the access of the database?
>
> any mysql variable I could use?
> or how can I load the index into memory? I have 32GB of ram XD plenty to
> useit into something more useful....

A configuration file would be helpful here.
>
> Thanks.
>


My guess is that you have a innodb table and that you have
unallocated innodb buffer pool. This is nothing more than a guess

What is ram XD?
--=20
Rob Wultsch
wultsch@gmail.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg

Re: Slow disk access: 1.4m to do a select count over 23GB table.

--0016361e829e886e52048b06b920
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

As usual, after you send a mail, you check for other things....

From the 32GB of ram, I only was allocating 2G, not by the process, but by
all the S.O...
free -G reported barely 1 gig of ram...

XD -> happy face that I have lots of ram...

now my face is like: ¬¬ -> why I didn't verfy the amount of ram earlier=
?

I'll verify this ram issue, cus if this is the issue then 1.4M isn't a bad
time...

TIA

unallocated innodb buffer pool. This is nothing more than a guess
>
> What is ram XD?
> --
> Rob Wultsch
> wultsch@gmail.com
>
My guess is that you have a innodb table and that you have

--0016361e829e886e52048b06b920--