Hi, On Fri, Feb 28, 2014 at 2:54 PM, Paul A <paul.a@navalmarinearchive.com> wrote:
At 12:59 PM 2/28/2014 -0800, Galen Charlton wrote:
We've found that it's the 'sessions' that accumulate. We cron it every morning at 3am, but I just ran it manually now (13.5 hours later) and get:
whoever@nelson:/usr/share/koha$ ./bin/cronjobs/cleanup_database.pl --sessions -v Session purge triggered. 55203 entries will be deleted. Done with session purge. [This is maybe [???] due to some bots that don't respect the robots.txt (baidu? I'm getting close to blocking them at router level)]
I'm personally fond of using the option to store sessions in memcached. But this is also an example of where innodb_file_per_table is nice, being able to run an 'optimize table session' would let you reclaim disk space. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org