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

* Your Email Address
* Spam protection	Enter the letters below: .__.. .. .. .._. \| \|\|_/ \|__\|\|\/\| \| \|__\\| \\| \|\| \|_\|_
Comment	> I'm running IMP using Horde VFS as the filestore for attachment > uploads. I'm using MySQL as the Horde VFS backend. > > > > When my horde_vfs table grew to 4GB in size, an apache process would > grow to almost 4GB in size when GC was run. This caused quite a bit > of thrashing on boxes that only have 4GB of memory. > > > > After looking at the code, when GC is run, with the SQL backend, it > ends up doing a select to load the whole table contents into memory. > This presumably gets put into a buffer in the mysql libs before being > loaded into PHP, and thus before the PHP memory limit can take effect. > > > > The unfortunate part is that all SQL needs for doing this cleanup is > a single DELETE statement, then the mysql server will do all the > work. As such, I suggest allowing each Horde VFS backend have its > own GC code.
Attachment
Watch this ticket