Has anyone experienced RedDot publishing taxing the server to the extent of causing problem loading the website?

[Kathleen Pottle]

We have found that RedDot publishing is taxing our server enough that
it causes us to loose connectivity for a short amount of time -
usually around 1 minute or so. During these times our site is not
accessible and just continues to try to load.

After the peak has gone by with the publishing process the site is
then available again.

Has anyone experienced similar publishing behavior?

Thanks,

Kathy Pottle
Phillips Exeter Academy
Exeter, NH

[Prasanth Nittala]

 Hi Kathy,

   Publishing is an intensive operation and might impact the site based on publishing. But firstly,

1) Which version of RedDot are you on?

2) Is it single server environment, with authoring server same as Publishing server?

 

Thanks,
Prasanth

 

 

--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
To post to this group, send email to reddot-c...@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.

[Kathleen Pottle]

Hi Prasanth,

 

Thank you for replying.

 

1) I believe we are on version 7.5 though I cannot find the version searching under settings. If you tell me where to find it I'll get that to you.

 

2) We do not have a separate publishing server. RedDot is on it's own dedicated server and the publishing starts there and publication is then pushed to our webprod server or the webqa server.

 

3) What is the specific recommendation for servers regarding RedDot and publishing?

 

Thank you,

Kathy Pottle

--
Kathleen S. Pottle
Offering Web & Office Solutions
(603) 502-7991

[Prasanth Nittala]

Hi Kathy,

 

1) You can find this information on the login page of your cms system. Version earlier than 9.0 version have page builder process, which is single threaded in ASP and is the bottleneck causing some performance issues, as it is used to construct pages for content editor when viewing/editing, as well as constructing the pages when publishing. It was migrated to .NET and improved since version 9.0.  

2) From what you described, I am assuming the previous issue you were mentioning about site not responding is in the perspective of content editors. 

3) There are several ways you can fine tune reddot to fix some of the performance issues in the environment. Please refer to this document -  http://oshyn.com/landingpages/performance-tuning-open-text that we have consolidated in improving the performance of the CMS.

4) Ways you can improve:

a) Cluster your CMS  by separating the Editorial server from the Publishing Server - this has some cost\licensing implications.

b) Upgrade your CMS from v7.5 to later versions which have .NET page builder process, which is in version 9.0 SP2 as to what i remember.

c) Performance tune the existing CMS -  http://oshyn.com/landingpages/performance-tuning-open-text

  

Several other options can be done based on your specific project settings. Hope it helps.

 

 Thanks,
Prasanth

-----Original Message-----
From: Kathleen Pottle <kspo...@gmail.com>
To: "Prasanth Nittala" <pnit...@oshyn.com>
Date: Mon, 3 Oct 2011 17:00:25 -0400
Subject: [reddot] Has anyone experienced RedDot publishing taxing the server to the extent of causing problem loading the website?

Hi Prasanth,

 

Thank you for replying.

 

1) I believe we are on version 7.5 though I cannot find the version searching under settings. If you tell me where to find it I'll get that to you.

 

2) We do not have a separate publishing server. RedDot is on it's own dedicated server and the publishing starts there and publication is then pushed to our webprod server or the webqa server.

 

3) What is the specific recommendation for servers regarding RedDot and publishing?

 

Thank you,

Kathy Pottle
 

On Mon, Oct 3, 2011 at 3:28 PM, Prasanth Nittala < pnit...@oshyn.com> wrote:

--
Kathleen S. Pottle
Offering Web & Office Solutions
(603) 502-7991

 

[Mark Radford]

Out of curiosity - do you mean the published website (as in the front-
end) is slow, or the CMS (RedDot) Website?

Mark

[Kathleen Pottle]

Published website...

--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
To post to this group, send email to reddot-c...@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.

[Mark Radford]

Is the site a .Net site? If so, the problem could be that the .aspx
pages you're publishing are causing the site to essentially restart.
Once they've been parsed by the .Net engine, they run nice and quickly
again, but immediately after publishing, it may take a while.

If it's not a .net site, then I'm not sure!

[Tony Gayter]

Yeah we had that, .net sites dont usually have a huge number of pages as its dynamic so when it restarted you dont really notice it, but as reddot outputs thousands (depending on the size of your site) it will bring it to a halt. There is a way round this (sort off). If you get the sections of your site to publish to subfolders this breaks up the site for .net and it will only parse the pages in each folder as you go into the section, this means the root (which would be the home page and maybe teh second level pages depending on how you publish) parse very quickly and you get performance back. Also it will only re-parse files in folders which have had files updated keeping other folders in cache.

[Mark Radford]

Good suggestion, Tony.

The other option is to publish the pages in other ways - rather than
publishing .aspx pages, you could publish the content as XML or text
fields and then dynamically display them. This requires a pretty
significant re-engineering of the way your site works, though (you'll
need URL re-writing for a start).

The folder option is certainly the best place to start!

Mark