Sounds like a very nice idea to me, but this could be a problem if temp
tables need to be bigger than RAM+Swap, which could easily be the case
in a table with 100,000,000 rows.
Gabriel PREDA schrieb:
For this table this is to late... leave it running...
If you want to do this on another
I have a table with ~100,000,000 rows. I recently discovered that I
need to start using one of the non-indexed columns in WHERE clauses. As
expected the performance is horrid. I decided to bite the bullet and
create an index (innodb):
mysql show full processlist\G
***
For this table this is to late... leave it running...
If you want to do this on another table(s)... and in general on huge
loaded MySQL servers I recomend the following...
Create a directory let's say /mnt/mem_fs
Mount in it /dev/shm use tmpfs as filesystem...
Now you have a directory that
OK, another one here...
On the very large table (at least 5 million rows) I need to index several columns.
The mysqladmin -i60 processlist
lists the state of the query as
Repair with keycache
for a very long time. I imagne it's sorting the indexes somehow.
My question is what variable
