Re: Table Locking Memory Engine
I have "INDEX(user,ip)" in that order and been using it.
After 5 mins if the ip hasn't went to a diffrent page or reloaded it deletes it so I would say within 30 mins the whole table is deleted and new rows are created by new users etc
It was innodb but I just recently switched to memory to prevent I/O no need for it really and seems to be quicker in all.
I'm not sure what Index timeout is? I looked it up at this time I never had it reject my request or timeout. It has aways loaded with the page and with about 3 days of server uptime ive only had "Failed attempts 2" out of millions of connections.
I'm still working on the cache this is what I have so far
query_cache_limit = 50M
query_cache_type=1
query_cache_limit=1048576
query_cache_size = 50M
Still needs tunning
Thanks rick!
Edited 3 time(s). Last edit at 08/09/2011 08:31PM by Daniel Oneil.
Subject
Written By
Posted
Re: Table Locking Memory Engine
August 09, 2011 08:21PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.