This was a big issue for us as well a while back. It got to the point that I had to cancel the FTP process from the DB so that the other pages could process. It would sometimes hang for 6 or more hours. I decided to take a different approach since there really wasn't a good reason that I HAD to use FTP to transfer the files. The first round of changes, I made new publishing jobs that would push the files out over a UNC path to the server instead of using FTP. This cut our publishing times in half!!! In an effort to make it even faster, rather than putting the load of moving files on our reddot server, I started dumping them locally on the reddot server and then used a product called Repliweb to move the files to their destinations. We have about 15 servers that need the files. I figured we could speed it up faster by removing the responsibility of pushing the files from CMS to some other independent process. It cut our publishing times down even further. By doing this we also stopped seeing the ftp process pop up in the asynchronous process list, clogging up publishing.
Hopefully that will give you a couple of ideas. Brett On Aug 28, 7:47 am, rwagner <[email protected]> wrote: > I want to throw this out to the big brains out there. > > We have a CMS nightly publication that is 6000+ pages and we expect to > take about three hours to publish to LiveServer. Lately, it's been > taking in excess of 12 hours, and sometimes we have to shut the job > down because it prevents publications from taking place the next day. > > The publication report in the CMS says "finished" but only displays > the media files published, no pages. After that it takes hours and > hours before an email gets send and the rest of the pub report fills > out. During this interval there is an async process called "FTP- > Transfer for PROJECT NAME" that sits in the async queue and does not > permit any other publication jobs to pass through. > > Has anyone out there seen something like this? If so, any ideas on > what might be causing it or how to approach fixing it? > > Much thanks for any help. > > -rw --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en -~----------~----~----~----~------~----~------~--~---
