We are having performance issue with content publishing in SDL Tridion R5.3.
As soon as I publish content from CMS server I could see content folder being dropped to the transport temp folder C:\transportemp. However it takes almost 120-140 seconds for the transport to pick up this content and process it. Have you ever experienced similar issues. Is there any settings where we could decrease the transport listener service time? So that as soon system drops a content, transport would be kicked off and package would be send to publishing immediately.
I'm running my tests in test server of 2GB RAM, 2 CPUs with 2.53 GHZ speed. Transport rendering and deployment number of threads in CMS server SDL Tridion MMC snap in is 2 COM+ recycle setting is 512 MB.Transport root temporary folder given in SDL Tridion MMC snapin is C:\transporttemp\
I ran this test with a content folder tcm_0-423535-63560.Content of size 150KB.
Below is the statistics of the same test.
At 7.52.20 AM folder of size 109 KB dropped in to transport root package folder C:\transporttemp
folder remained stationary in C:\transporttemp folder for 131 seconds.
transport started at [Debug 10-10-2012 07:54:31] transport ended at [Debug 10-10-2012 07:54:41]
time taken for transport- 10 seconds
deployment started at [Debug 10-10-2012 07:54:32] deployment ended at [Debug 10-10-2012 07:54:39] time taken for deployment- 7seconds
Appreciate your help on this. Thanks, KK
Typically you notice this behavior when you have lot of temp directory files and/or your transactions files did not get cleanup. You could check these folder locations for files/folders start with
tcm.You could setup some scheduled job to clean these folders on regular basis as part of your maintenance tasks.
The folders are typically
What type of transport mechanism you are using?
httpsftpetc? Also, check if the package transfer is not taking time to upload to deployer (I do not know the package size, but 10 secs is not common for simple publishing packages).