Thanks scott ... <div><br></div><div>This time we will track why it's been slow ..</div><div><br></div><div>Thanks,</div><div>Dinesh..<br><br><div class="gmail_quote">On Sat, Jun 9, 2012 at 4:40 AM, Scott Marlowe <span dir="ltr"><<a href="mailto:scott.marlowe@gmail.com" target="_blank">scott.marlowe@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Fri, Jun 8, 2012 at 3:30 PM, dinesh kumar <<a href="mailto:dineshkumar02@gmail.com">dineshkumar02@gmail.com</a>> wrote:<br>
> Hi Steve,<br>
><br>
> Thank you for the e-mail ..<br>
><br>
> On Sat, Jun 9, 2012 at 1:39 AM, Steve Singer <<a href="mailto:ssinger@ca.afilias.info">ssinger@ca.afilias.info</a>><br>
> wrote:<br>
>><br>
>> On 12-06-08 02:50 PM, dinesh kumar wrote:<br>
>>><br>
>>> Thank you so much Steve ...<br>
>>><br>
>>> We are using Slony 2.1.x ... We are still at the initial stage only...<br>
>>> Slony is still trying to copy the data from source to destination host ..<br>
>>><br>
>>> >> Has your initial copy_set finished?<br>
>>><br>
>>> Here only, we are facing problem... Slony struggling to copy the data ..<br>
>>> It went well upto 140 GB. From 141GB onwards the build started slow..<br>
>>> Now it's very very very slow ...<br>
>>><br>
>>> Let me know if you need any configurations what we have used ...<br>
>>><br>
>><br>
>> Are you doing this copy over a WAN?<br>
><br>
><br>
> We are doing copy over LAN.. We got very good transfer rate for up to some<br>
> extent.. From after some time (i'm not sure the exact time), the build got<br>
> slow..<br>
<br>
</div>We need to know why.<br>
<div class="im"><br>
>> Can you tell what the bottleneck is? Are you IO bound on the slave? Are<br>
>> you CPU bound on the slave?<br>
>><br>
> We don't face any performance issues. IO is really good on<br>
> production(Primary Cluster where it is 3 TB) and having normal CPU average<br>
<br>
</div>What does iostat -xd 10 or such have to say about the performance on<br>
the new slony destination when it's slow?<br>
<div class="im"><br>
> We think, it's problem from the db itself.. We have around 400GB tables (5<br>
> to 8), those are having huge bloats also.. We think, slony is taking some<br>
> time to get those live rows bypassing the dead rows from DB. So we think,<br>
> the actual live rows might scatter to multiple files. I think this might be<br>
> the root cause ..<br>
<br>
</div>I doubt bloat in the source database would make things 1GB/hr slow.<br>
That's only 16MB/minute.<br>
<div class="im"><br>
> We just stopped the existing slony setup and will perform vacuum on DB once<br>
> and will do it again ...<br>
<br>
</div>Yeah, this time try and figure out what the bottleneck is via iostat,<br>
vmstat, iotop, nettop, select * from pg_stat_activity and so on.<br>
</blockquote></div><br></div>