EPrints Technical Mailing List Archive

Message: #01524

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] Re: size of tables in mysql

So, as part of a migration from 3.1 to 3.3, would emptying access__ordervalues_en be a useful step before starting the database upgrade?
Our table is ~2G.

Cheers,
John

-----Original Message-----
From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Tim Brody
Sent: 05 February 2013 16:10
To: eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] Re: size of tables in mysql

On Tue, 2013-02-05 at 13:47 +0100, Yuri wrote:
> -rw-rw---- 1 mysql mysql 2,7G  5 feb 13:45 
> /var/lib/mysql/mysite/access__ordervalues_en.MYD
> 
> is this a normal value for a 40000 thesis site with 10 millions of pdf 
> download at year?
> *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
> *** Archive: http://www.eprints.org/tech.php/
> *** EPrints community wiki: http://wiki.eprints.org/

What version of EPrints is this in?

On a recent 3.3 access__ordervalues_en should no longer be populated,
and can be safely cleared. It's on our "TODO" to tidy up historical
access log data (i.e. throw away more robots & other junk data).

-- 
All the best,
Tim