tuning RSS

We're bringing up some RSS servers and pushing them all to one box on smaller instances that (in the case of DR) will be moved to larger boxes not currently available. How much smaller can I make these "catcher" RSS secondaries? We've had them smaller before, but they seemed too small and would run out of memory. We don't want full exact config copies there because they are too large. Any advice? Thanks in advance, Nate

My advice? Make the RSS secondaries as big as the primaries. Or, if this is temporary, the take the size of the primary, factor in the percentage of total resources on the primary are being actively used, and size the secondaries that way. So, for example, if a primary server is running 16 CPU VPs on an 8 core machine and the processor cores are never more than 50% loaded at peak load, then you could get away with a secondary with only 4 cores and 8 CPU VPs. Memory, however, is going to be whatever amount of memory is being used on the primary. So if the primary has 8GB of cache and an 8GB virtual segment, but the virtual segment is 50% free then the secondary can probably get away with only a 4GB virtual segment but keep the full 8GB cache. Keep in mind that you may be thinking "It's just temporary, and it's only a secondary.", but if the primary fails you WILL have to run your production load on the secondary and your users and managers will NOT forgive you for slowing down the business just because you saved them a few thousand bucks! Oh, and don't fall into the trap of saying "But there will be multiple secondary instances on one physical box backing up multiple primaries on separate machines! So, I only need one full sized machine to run all of them!" That will only work until you lose two servers in the same day or some nitwit unplugs a SAN supplying data to all of your primaries (yes, I've seen it happen), or some jackass decides to pull the router off the network in the middle of the day to install an newer faster one so he doesn't have to stay late (yup seen this one too). Your secondaries MUST be AT LEAST as powerful and capable as your primary servers, because one day they may become your primary servers and it may last more than a single day! Art Art S. Kagel, Principal Consultant Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Mon, Oct 14, 2013 at 2:28 PM, NATE HICKS <nathaniel.hicks@trnswrks.com>wrote: > We're bringing up some RSS servers and pushing them all to one box on > smaller > instances that (in the case of DR) will be moved to larger boxes not > currently > available. How much smaller can I make these "catcher" RSS secondaries? > We've > had them smaller before, but they seemed too small and would run out of > memory. We don't want full exact config copies there because they are too > large. Any advice? > > Thanks in advance, > > Nate > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --089e01227ca400974504e8b8568a