<div>Thanks, Scott & Steve for this clues!</div>
<div>My situation is not the PgSQL 8.0.x one, I have 8.4.x x64 installed, and the replication schema uses an internet connection between two DB's, a master & a slave.</div>
<div>Sometimes, the replication seems to stop working, I'm trying to figure out what's wrong, if there is something.</div>
<div>I'll start a shell script right now to check the master & slave systems based on the clues you sent.</div>
<div>Thanks again, and best regards,</div>
<div> </div>
<div>HeCSa.</div>
<div><br><br> </div>
<div class="gmail_quote">On Mon, Jun 14, 2010 at 6:01 PM, Steve Singer <span dir="ltr"><<a href="mailto:ssinger@ca.afilias.info">ssinger@ca.afilias.info</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div class="im">Hernan Saltiel wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote"><br>How can I meassure how much is too much use of my hardware when Slony is in place?<br>I can meassure the CPU, memory, disk IO, and network use, but how much is needed in order to let Slony work well?<br>
Is there any way to calculate this on a transaction number and size basis?<br>Thanks!<br></blockquote><br></div>The other thing you should look into is if your having performance issues on your database from improper/insufficient vacuuming. Back in the 8.0 days vacuuming issues where pretty common (I think 8.0 was before auto-vacuum or at least before auto-vacuum got good).<br>
<br>Are your application tables bloated?<br>Are your slony tables bloated?<br>Are your vacuum processes taking a long time?<br>If your've had vacuum issues in the past have you exceeded the size you've allocated to the free-space map.<br>
<br>Vacuuming the entire database through a single "VACUUM" command launched from cron is somtimes not the best approach, sometimes you need to issue individual vacuum commands on a per table basis where some tables get hit frequently (maybe a few times an hour) while others might only get vacuumed once a week. It all depends on the acccess patterns to the tables and with older versions of postgresql the DBA is often left to figure this out on their own.<br>
<br>Also slony should be issuing vacuum commands against the slony tables so you probably don't want 'other' vacuum commands that regularly get run to duplicate the work.<br><br><br><br><br><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div class="im"> <br><br> > Can someone point me where should i look into and how to improve<br> replication<br> > performance.<br><br> More / faster drives and controllers.<br><br> > As of now there is no chance for upgradation of version.<br>
<br> That would be the first thing I'd recommend. Since you can't do it,<br> you're gonna have to have faster hardware, specifically the IO<br> subsystem.<br> _______________________________________________<br>
Slony1-general mailing list<br></div> <a href="mailto:Slony1-general@lists.slony.info" target="_blank">Slony1-general@lists.slony.info</a> <mailto:<a href="mailto:Slony1-general@lists.slony.info" target="_blank">Slony1-general@lists.slony.info</a>>
<div class="im"><br> <a href="http://lists.slony.info/mailman/listinfo/slony1-general" target="_blank">http://lists.slony.info/mailman/listinfo/slony1-general</a><br><br><br><br><br>-- <br>HeCSa<br><br><br></div>------------------------------------------------------------------------
<div class="im"><br><br>_______________________________________________<br>Slony1-general mailing list<br><a href="mailto:Slony1-general@lists.slony.info" target="_blank">Slony1-general@lists.slony.info</a><br><a href="http://lists.slony.info/mailman/listinfo/slony1-general" target="_blank">http://lists.slony.info/mailman/listinfo/slony1-general</a><br>
</div></blockquote><font color="#888888"><br><br>-- <br>Steve Singer<br>Afilias Canada<br>Data Services Developer<br>416-673-1142<br></font></blockquote></div><br><br clear="all"><br>-- <br>HeCSa<br>