[Tickets #4797] Re: A large horde_vfs table can cause large memory usage during GC

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://dev.horde.org/horde/whups/ticket/?id=4797
-----------------------------------------------------------------------
 Ticket             | 4797
 Updated By         | sean at duke.edu
 Summary            | A large horde_vfs table can cause large memory usage during GC
 Queue              | Horde Framework Packages
 Version            | HEAD
 Type               | Bug
 State              | Feedback
 Priority           | 2. Medium
 Owners             | 
-----------------------------------------------------------------------


sean at duke.edu (2006-12-20 13:33) wrote:

Here's what I'm using in an hourly cron job (put in place to work around
this bug):

THRESHOLD=`date -d "12 hours ago" +%s`
DEL_COMMAND="DELETE FROM horde_vfs WHERE vfs_path = '.horde/imp/compose'
AND vfs_modified < ${THRESHOLD}"


After doing this, I'm thinking it might be better to replace the 'vfs_path
= '.horde/imp/compose'' check with a check on the vfs_type.   The main
concern I have here is not deleting the directories.    This works for the
IMP application.  It may need to be made more robust for a general use
statement.