Discussion:
[EP-tech] Cachemap table filling quickly -- help!
Betsy Coles
2010-06-30 17:40:08 UTC
Permalink
Hi,

We have noticed severe slowness in our CaltechAUTHORS repository today (running EPrints 3.1.3). The cachemap table has more than 300 entries in it-way more than normal, and it's growing rapidly. Normally, I would expect to see a reasonable search expression in cachemap table entries, something like:

| 6869422 | 1277916890 | 1277916891 | NULL | 0|1|-date/creators_name/title|archive|-|creators_name:creators_name:ALL:IN:"Rutledge, D"|-|eprint_status:eprint_status:ALL:EQ:archive|metadata_visibility:metadata_visibility:ALL:EX:show

However, more than 200 of the current entries look exactly like this:

| 6868305 | 1277905355 | 1277905356 | NULL | 1|1|-datestamp|archive|-|-|eprint_status:eprint_status:ALL:EQ:archive|metadata_visibility:metadata_visibility:ALL:EX:show(reordered:-datestamp)

I don't pretend to understand what exactly the cache tables or cachemap table are doing, but this doesn't seem right. Can anyone explain


1) What is going on here, and

2) How can I clear the cache/cachemap tables without just waiting for them to expire?

Thanks in advance,

Betsy Coles
Caltech Library IT Group
***@caltech.edu
Tim Brody
2010-07-01 08:18:07 UTC
Permalink
Post by Betsy Coles
Hi,
We have noticed severe slowness in our CaltechAUTHORS repository today
(running EPrints 3.1.3). The cachemap table has more than 300 entries
in it—way more than normal, and it’s growing rapidly. Normally, I
would expect to see a reasonable search expression in cachemap table
| 6869422 | 1277916890 | 1277916891 | NULL | 0|
1|-date/creators_name/title|archive|-|
creators_name:creators_name:ALL:IN:"Rutledge, D"|-|
eprint_status:eprint_status:ALL:EQ:archive|
metadata_visibility:metadata_visibility:ALL:EX:show
| 6868305 | 1277905355 | 1277905356 | NULL | 1|1|-datestamp|
archive|-|-|eprint_status:eprint_status:ALL:EQ:archive|
metadata_visibility:metadata_visibility:ALL:EX:show(reordered:-datestamp)
I don’t pretend to understand what exactly the cache tables or
cachemap table are doing, but this doesn’t seem right. Can anyone
explain
1) What is going on here, and
My guess would be robots hitting your RSS/Atom feeds (which corresponds
to that search query above).
Post by Betsy Coles
2) How can I clear the cache/cachemap tables without just waiting
for them to expire?
There isn't a tool in 3.1 to wipe cachemap tables. But you could expire
them all by doing:
UPDATE cachemap SET created=0, lastused=0;
(Then do a search and click to at least the 2nd page of results)

All the best,
Tim.

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wik

Loading...