<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Problems with Sitecore and the staging module part 1.</title>
	<atom:link href="http://blog.paulgeorge.co.uk/2009/07/22/problems-with-sitecore-and-the-staging-module/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.paulgeorge.co.uk/2009/07/22/problems-with-sitecore-and-the-staging-module/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=problems-with-sitecore-and-the-staging-module</link>
	<description>Web developer, based in London. Mainly working with ASP.net and Sitecore CMS.</description>
	<lastBuildDate>Tue, 24 Jan 2012 15:02:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: paulg</title>
		<link>http://blog.paulgeorge.co.uk/2009/07/22/problems-with-sitecore-and-the-staging-module/#comment-50</link>
		<dc:creator>paulg</dc:creator>
		<pubDate>Tue, 19 Apr 2011 13:41:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulgeorge.co.uk/?p=101#comment-50</guid>
		<description>Note: This from memory - if there are loads of xml files (each representing a job to be processed), it probably means there is no scheduled task reading &amp; deleting them. Or perhaps they are being generated (by a publishing action) faster than they are being processed (by a scheduled task) i.e. task interval is too slow/long or publishing interval too fast...

Much better: just upgrade to a point where you can use the in-built scaling solution.</description>
		<content:encoded><![CDATA[<p>Note: This from memory &#8211; if there are loads of xml files (each representing a job to be processed), it probably means there is no scheduled task reading &amp; deleting them. Or perhaps they are being generated (by a publishing action) faster than they are being processed (by a scheduled task) i.e. task interval is too slow/long or publishing interval too fast&#8230;</p>
<p>Much better: just upgrade to a point where you can use the in-built scaling solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke Wilkinson</title>
		<link>http://blog.paulgeorge.co.uk/2009/07/22/problems-with-sitecore-and-the-staging-module/#comment-49</link>
		<dc:creator>Luke Wilkinson</dc:creator>
		<pubDate>Tue, 19 Apr 2011 13:11:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulgeorge.co.uk/?p=101#comment-49</guid>
		<description>Nice blog, you say that if w&quot;If there are loads of .xml files you probably have another problem&quot; - If this is the case what is the problem?</description>
		<content:encoded><![CDATA[<p>Nice blog, you say that if w&#8221;If there are loads of .xml files you probably have another problem&#8221; &#8211; If this is the case what is the problem?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Publishing and Cache Clearing Basics &#171; Sitecore basics!</title>
		<link>http://blog.paulgeorge.co.uk/2009/07/22/problems-with-sitecore-and-the-staging-module/#comment-18</link>
		<dc:creator>Publishing and Cache Clearing Basics &#171; Sitecore basics!</dc:creator>
		<pubDate>Tue, 12 Apr 2011 01:29:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulgeorge.co.uk/?p=101#comment-18</guid>
		<description>[...] http://blog.paulgeorge.co.uk/2009/07/22/problems-with-sitecore-and-the-staging-module/ [...] </description>
		<content:encoded><![CDATA[<p>[...] <a href="http://blog.paulgeorge.co.uk/2009/07/22/problems-with-sitecore-and-the-staging-module/" rel="nofollow">http://blog.paulgeorge.co.uk/2009/07/22/problems-with-sitecore-and-the-staging-module/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://blog.paulgeorge.co.uk/2009/07/22/problems-with-sitecore-and-the-staging-module/#comment-17</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Thu, 16 Dec 2010 09:33:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulgeorge.co.uk/?p=101#comment-17</guid>
		<description>Thanks for this - you&#039;re not wrong  - we have seen the staging module full cache clearance cripple a site with a full cache clearance.

However Sitecore have now assured me that the latest version of staging module works correctly with partial cache clearance. The updated documentation is here:

http://sdn.sitecore.net/upload/sdn5/modules/staging/staging_module_installation_and_configuration_guide_sc6_a4.pdf

I&#039;ve not tried it yet but will be trying it out soon, I&#039;ll keep you informed.</description>
		<content:encoded><![CDATA[<p>Thanks for this &#8211; you&#8217;re not wrong  &#8211; we have seen the staging module full cache clearance cripple a site with a full cache clearance.</p>
<p>However Sitecore have now assured me that the latest version of staging module works correctly with partial cache clearance. The updated documentation is here:</p>
<p><a href="http://sdn.sitecore.net/upload/sdn5/modules/staging/staging_module_installation_and_configuration_guide_sc6_a4.pdf" rel="nofollow">http://sdn.sitecore.net/upload/sdn5/modules/staging/staging_module_installation_and_configuration_guide_sc6_a4.pdf</a></p>
<p>I&#8217;ve not tried it yet but will be trying it out soon, I&#8217;ll keep you informed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek Roberti</title>
		<link>http://blog.paulgeorge.co.uk/2009/07/22/problems-with-sitecore-and-the-staging-module/#comment-16</link>
		<dc:creator>Derek Roberti</dc:creator>
		<pubDate>Thu, 25 Mar 2010 16:42:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulgeorge.co.uk/?p=101#comment-16</guid>
		<description>Hi Kiran,

To simplify your implementation, you may consider the latest version of the staging module. It incorporates the partial cache clearing and the movement of files.

Since Sitecore Stage is Shared Source (and, hence, unsupported), getting on track with the latest version of the Staging Module may be the way to go.

Best wishes,
Derek</description>
		<content:encoded><![CDATA[<p>Hi Kiran,</p>
<p>To simplify your implementation, you may consider the latest version of the staging module. It incorporates the partial cache clearing and the movement of files.</p>
<p>Since Sitecore Stage is Shared Source (and, hence, unsupported), getting on track with the latest version of the Staging Module may be the way to go.</p>
<p>Best wishes,<br />
Derek</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kiran Patil</title>
		<link>http://blog.paulgeorge.co.uk/2009/07/22/problems-with-sitecore-and-the-staging-module/#comment-15</link>
		<dc:creator>Kiran Patil</dc:creator>
		<pubDate>Thu, 25 Mar 2010 06:05:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulgeorge.co.uk/?p=101#comment-15</guid>
		<description>Hi Paul George,

Really nice blog!

We are also facing same kind of issues sometime our front end servers shows &quot;504 - Gateway Timeout&quot; error. But we have configured something different which is as below:

1. Staging Module : - For upload and download sublayout files.
2. Stager Module :- For clearing cache partially. http://trac.sitecore.net/SitecoreStager

Now, our cache clearing stuff is totally managed by SiteCoreStager module. But sometimes our published changes dosen&#039;t reflects up on front end servers which forces us to iisreset -- which we would like to avoid.

Can you pls help us out. How it should be managed?

Thanks a lot,
Kiran Patil</description>
		<content:encoded><![CDATA[<p>Hi Paul George,</p>
<p>Really nice blog!</p>
<p>We are also facing same kind of issues sometime our front end servers shows &#8220;504 &#8211; Gateway Timeout&#8221; error. But we have configured something different which is as below:</p>
<p>1. Staging Module : &#8211; For upload and download sublayout files.<br />
2. Stager Module :- For clearing cache partially. <a href="http://trac.sitecore.net/SitecoreStager" rel="nofollow">http://trac.sitecore.net/SitecoreStager</a></p>
<p>Now, our cache clearing stuff is totally managed by SiteCoreStager module. But sometimes our published changes dosen&#8217;t reflects up on front end servers which forces us to iisreset &#8212; which we would like to avoid.</p>
<p>Can you pls help us out. How it should be managed?</p>
<p>Thanks a lot,<br />
Kiran Patil</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Publishing strategies &#171; Molten Core</title>
		<link>http://blog.paulgeorge.co.uk/2009/07/22/problems-with-sitecore-and-the-staging-module/#comment-14</link>
		<dc:creator>Publishing strategies &#171; Molten Core</dc:creator>
		<pubDate>Thu, 21 Jan 2010 23:11:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulgeorge.co.uk/?p=101#comment-14</guid>
		<description>[...] One of the issues with publishing can be performance. When you publish one or more items the HTML cache is cleared, which means that if you have some performance heavy presentations, it will increase the loading time of the page, until the cache has been rebuild. Further if you use the staging module and it is configured to it, all the data caches are cleared as well. This can cause the site to take up to 30 seconds to reload your pages – especially if they are data heavy. You can read more about Sitecore Caching here and read about the issues with cache and the staging module here. [...] </description>
		<content:encoded><![CDATA[<p>[...] One of the issues with publishing can be performance. When you publish one or more items the HTML cache is cleared, which means that if you have some performance heavy presentations, it will increase the loading time of the page, until the cache has been rebuild. Further if you use the staging module and it is configured to it, all the data caches are cleared as well. This can cause the site to take up to 30 seconds to reload your pages – especially if they are data heavy. You can read more about Sitecore Caching here and read about the issues with cache and the staging module here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek Roberti</title>
		<link>http://blog.paulgeorge.co.uk/2009/07/22/problems-with-sitecore-and-the-staging-module/#comment-13</link>
		<dc:creator>Derek Roberti</dc:creator>
		<pubDate>Tue, 29 Sep 2009 16:49:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulgeorge.co.uk/?p=101#comment-13</guid>
		<description>Hi Paul,

Thanks for your thoughtful analysis of the Sitecore Staging Module in this and in Part II. If you are using Sitecore 6, you might consider trying the Sitecore Stager, which can be found in Sitecore&#039;s Shared Source Library. The Stager provides item-level cache clearing and, as a result, does not trigger the full cache clearing that you describe in your article.

Two more notes: 1) The Sitecore Stager does not replace the FTP/SOAP file transfer functionality that is part of the Staging Module. 2) The Sitecore Stager does clear the HTML cache, but not the item cache. So, if you use XSLT, the transformations will be processed again; but the database won&#039;t be hit as with the standard Staging Module.

Best wishes,
Derek</description>
		<content:encoded><![CDATA[<p>Hi Paul,</p>
<p>Thanks for your thoughtful analysis of the Sitecore Staging Module in this and in Part II. If you are using Sitecore 6, you might consider trying the Sitecore Stager, which can be found in Sitecore&#8217;s Shared Source Library. The Stager provides item-level cache clearing and, as a result, does not trigger the full cache clearing that you describe in your article.</p>
<p>Two more notes: 1) The Sitecore Stager does not replace the FTP/SOAP file transfer functionality that is part of the Staging Module. 2) The Sitecore Stager does clear the HTML cache, but not the item cache. So, if you use XSLT, the transformations will be processed again; but the database won&#8217;t be hit as with the standard Staging Module.</p>
<p>Best wishes,<br />
Derek</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aboo Bolaky</title>
		<link>http://blog.paulgeorge.co.uk/2009/07/22/problems-with-sitecore-and-the-staging-module/#comment-12</link>
		<dc:creator>Aboo Bolaky</dc:creator>
		<pubDate>Tue, 28 Jul 2009 21:17:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulgeorge.co.uk/?p=101#comment-12</guid>
		<description>Dude,
I haven&#039;t yet worked with the Staging Module but I&#039;m sure that if ever I get to work with it someday, I&#039;ll get in touch with you. It&#039;s quite clear that you must have really  been frustrated whilst working with this module. Look at the bright side... No pain, No gain !!!</description>
		<content:encoded><![CDATA[<p>Dude,<br />
I haven&#8217;t yet worked with the Staging Module but I&#8217;m sure that if ever I get to work with it someday, I&#8217;ll get in touch with you. It&#8217;s quite clear that you must have really  been frustrated whilst working with this module. Look at the bright side&#8230; No pain, No gain !!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

