We do publishing on demand pretty much 24/7... if you have downtime meaning you can afford to do a full publish of your site nightly when the users aren't updating content than maybe you don't need a separate publishing server. We have 2 in our setup and it makes a big difference. Red Dot is incredibly IO bound all those temp files it writes to disk.... if you can afford to buy licences for a publication server from the get go I'd suggest you do it. Our setup consists of 3 servers 1 dedicated for database, 1 for just the Red Dot front end (editorial server), and one Red Dot server dedicated for publishing and admin tasks. What you'll notice if you work allot with keyword lists is that once you start accumulating content after your project has launched tagging/untagging keyword lists becomes very taxing on a server... if you have to add/remove 300-900 items for each keyword you add/remove from a list.
On Mar 19, 9:58 am, "Killingsworth, Chad A" <[email protected]> wrote: > I'm curious; for those people who have a second publishing server, do you > publish on demand or do a full publish every night? > > We have a lot of content and a large number of CMS users and have never seen > the need for a second publishing server. > > Chad Killingsworth > Assistant Director of Web & New Media > Missouri State University > > From: [email protected] > [mailto:[email protected]] On Behalf Of Keith Bloom > Sent: Friday, March 19, 2010 8:44 AM > To: [email protected] > Subject: Re: RedDot system requirements > > I think the PageBuilder process and SQL server stamp all over each other for > resources on the server, and that Disk IO is the one which gets really > hammered. It may be possible to achieve good performance with two disk > arrays in the server and a whole lot of RAM but if you're going down that > road you may as well just use two servers for the job. > > In fact the publishing process is so heavy weight RedDot recommended we have > two RedDot servers. One for content editing (0 asynchronous processes) and > one for publishing tasks (as many asynchronous process as the server will > take). Plus a separate box for SQL. > > Of course I'm sure this had nothing to do with sale of another server licence > :) > > Keith. > On 19 March 2010 13:32, > [email protected]<mailto:[email protected]> > <[email protected]<mailto:[email protected]>> wrote: > I've always heard this maxim, and follow it myself, but I've always > been curious about WHY separating them yields better performance. > You'd think that things would be smoother if the data didn't have to > travel over a network between storage and processing, but I guess it's > not the case. > > Ed > > On Mar 10, 12:50 pm, "Prasanth Nittala" > <[email protected]<mailto:[email protected]>> wrote: > > > > > > > Hi Bobby, > > > CMS and SQL Server being seperate servers is the way to go for enterprise > > standards. Else you would encounter performance issues. This is better from > > architectural perspective in terms of scalability and extensibility. > > Thanks, > > Prasanth------------------------------------------------------------------- > > - > > Prasanth Nittala > > 213-814-4163 |www.oshyn.com<http://www.oshyn.com> > > > -----Original Message----- > > > From: bobbykjack <[email protected]<mailto:[email protected]>> > > > To: "Prasanth Nittala" <[email protected]<mailto:[email protected]>> > > > Date: Wed, 10 Mar 2010 07:01:48 -0800 (PST) > > > Subject: [reddot] RedDot system requirements > > > Just a quick straw poll: are you running RedDot CMS and MS SQL Server > > > on the same physical server, or multiple boxes? Any recommendations or > > > problems suffered with either approach? > > > Thanks, > > > - Bobby > > > -- > > > 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]<mailto:[email protected]> > > . > > > To unsubscribe from this group, send email to > > [email protected]<mailto:reddot-cms-users%2Buns > > [email protected]>. > > > For more options, visit this group > > athttp://groups.google.com/group/reddot-cms-users?hl=en<http://groups.google.com/group/reddot-cms-users?hl=en> > > [http://groups.google.com/group/reddot-cms-users?hl=en]. > > -- > 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]<mailto:[email protected]> . > To unsubscribe from this group, send email to > [email protected]<mailto:reddot-cms-users%2Buns > [email protected]>. > For more options, visit this group > athttp://groups.google.com/group/reddot-cms-users?hl=en. > > -- > 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 > athttp://groups.google.com/group/reddot-cms-users?hl=en. -- 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.
