On 2011-07-16 16:43, Ignoramus29044 wrote:
Have you considered range partitioning?

http://dev.mysql.com/doc/refman/5.1/...ing-range.html


/Lennart

[...]

On 2011-07-16, Lennart Jonsson <erik.lennart.jonsson (AT) gmail (DOT) com> wrote:
That sounds like a good plan. Another idea to keep in mind is to have
a separate table, such as

bigtable_date DATE,
bigtable_id bigint

and select from this table and do single deletes (or group deletes) on
the big table.

Maybe it is better than DELETE ... LIMIT ...?

El 16/07/2011 16:43, Ignoramus29044 escribió/wrote:
If the whole table is getting locked, you are probably using MyISAM. In
such case, you might be able to benefit from the LOW_PRIORITY and QUICK
clauses:

http://dev.mysql.com/doc/refman/5.5/en/delete.html

See also:

http://dev.mysql.com/doc/refman/5.5/...ete-speed.html


--
-- http://alvaro.es - Álvaro G. Vicario - Burgos, Spain
-- Mi sitio sobre programación web: http://borrame.com
-- Mi web de humor satinado: http://www.demogracia.com
--

On 7/16/2011 7:43 AM, Ignoramus29044 wrote:
One of the simplest solutions is, rather than doing a big delete
infrequently, do a small delete frequently. If you want to delete
entries more than 30 days old, do it every day, or more frequently
if necessary. If the WHERE expression is one that executes fast
(like "mydate < '2011-03-01'", assuming "mydate" is indexed),
this is cheap. If you run more than once a day, try
like "mydate < TIMESTAMPADD(DAY,-31,NOW())", which is exactly
31 days ago.

Partitioning is an option. but may be overkill.

John Nagle

On 20-07-2011 22:31, John Nagle wrote:
i tried to suggest that 4 days ago, but i'm not that good in explaining

--
Luuk