So the gist of it is that the FTP process that moves files to LiveServer is a clunker. I certainly think that it's a flaw in the system to have only one part of the two-part publication process be multi-threaded. A full-site publish should not be jamming up additional publications.
It is helpful just knowing I'm not alone in this. However, I have been getting some conflicting feedback. Some people are saying that "releasfilesatonce=true" config setting is faster. and some are saying it causes problems. Not sure how to reconcile that. On Aug 28, 9: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 -~----------~----~----~----~------~----~------~--~---
