Code / The Appnel Group 

Bummer

Recently the MT 4.1 release notes where amended with a new important advisory for systems using the PublishQueue and/or FastCGI.

Advisories

• Due to a memory leak in Movable Type template parser, large scale web sites are advised not to use Publish Queue in daemon mode or FastCGI for the time being.

This news is a bit old, but worth noting since it will eventually bring a server to its knees. That is a bummer. For most users there is little impact sine run through CGI the leak memory gets cleaned up after each request. This is a problem for optimized and high performance systems like the ones I and other ProNetters build.

I had hoped that a fix/patch was released by now, but it hasn’t to date. I have ti on good word this is actively being worked out. I also know the community has made their offerings and there has been some activity in the public repository to this affect though. In the meanwhile you may want to take precautionary measures such as not using the PublishQueue and, if you are running FastCGI, periodically restarting your web server to clear out the leaked memory.

Hi Tim --

We see this as well re-publishing a site with 35,000+ entries, since each job maps to pubilshing individual archives (all 35k), publishing the category archives, etc.

From the docs:

>-load
>Takes as input an integer which indicates the number of jobs to process at one >time. This option is only valid when running in daemon mode. The default is 10.

but shouldn't each job simply be a republish of a single page? Taking 10 off the queue at a time then wouldn't have perl sitting around trying to publish 35k pages at a time. Does seem to work this way right now, though.