What is the _wiw_m table for?

duck · Worker Joined: Jul 03, 2006 Posts: 247

Just curious what is this tables purpose?

Palbin · Posted: Wed Sep 16, 2009 10:19 am

It is a a Memory/HEAP table that is used for the Who is Where block.

dad7732 · Posted: Mon Oct 19, 2009 11:59 am

... and if you do a MySQL optimize it will show errors for those tables but not to worry, it's supposed to show errors.

Raven · Posted: Tue Oct 20, 2009 12:33 am

There is really no reason to store this data in the database and incur more MySQL overhead so I just load it into memory for super fast access Smile

unicornio · Involved Joined: Aug 13, 2009 Posts: 410

What is the file who calls that kind of table?

Palbin · Posted: Tue Oct 20, 2009 12:17 pm

Look in the block and i think there are two files within the includes folder. i can't remember the name, but they should be named as such you should recognize them.

Raven · Posted: Tue Oct 20, 2009 12:20 pm

Any file you want. It acts just like a MySQL table with certain, but not imposing, restrictions. See

Only registered users can see links on this board!
Get registered or login to the forums!

for more information.

unicornio · Involved Joined: Aug 13, 2009 Posts: 410

Wow! This is really interesting. I found the files. Now I understand what is the meaning. Very Happy

How clever you are. lol

Raven · Posted: Tue Oct 20, 2009 12:44 pm

It will speed up nuke to the extent that the MySQL table I/O is sped up. Memory tables do not incur anywhere near the overhead for ISAM operations. But, they are not a general replacement for ISAM tables as they are limited as described in the link above. However, I use them in a couple of places and with hundreds of rows of non-indexed addressing and they are faster than ISAM table storage even w/o indexes.

unicornio · Involved Joined: Aug 13, 2009 Posts: 410

Raven. Can you update Cache Lite addon so we can speed up a little bit more loading blocks. Thanks in advance.

Quote:

It will speed up nuke to the extent that the MySQL table I/O is sped up. Memory tables do not incur anywhere near the overhead for ISAM operations. But, they are not a general replacement for ISAM tables as they are limited as described in the link above. However, I use them in a couple of places and with hundreds of rows of non-indexed addressing and they are faster than ISAM table storage even w/o indexes.

Now I realize why RaveNuke is loading so fast. Cheers Very Happy