On Fri, Jan 3, 2014 at 5:03 PM, Scott Marlowe <scott.marlowe at gmail.com>wrote:

> On Thu, Jan 2, 2014 at 12:35 PM, Tory M Blue <tmblue at gmail.com> wrote:
> >
> > Wondering what settings I need to speed this up. To do a rebuild of a db
> it
> > takes a long time, 6 hours for a singe  table. No I/O issues, no load,
> just
> > slon postgres taking their sweet old time. I would like to use the
> resources
> > available to speed this up.
>
> 1: How fast can you scp a file between these two boxes?
> 2: How far apart are they / is there a lot of latency between them?
> 3: How fast can you create a good sized file on the slave? (dd
> if=/etc/zero of=bigfile bs=1000000 count=1000)
>
> If they are far apart then make sure your slon daemon is running on
> the slave not the master. This can make a huge difference.
>
> > #sync_max_rowsize=8192
>
> Try turning this up to 32768 as well.
>

1) Very quick , Accessing an iscsi volume I can scp  the bigfile across at
roughly 45MB/s, so plenty.
2) Again same segment, nothing in the way
3) ISCSI volume (ISCSI device is running at roughly 6GB network speed)
 [user at idb02 tmp]# time dd if=/dev/zero of=bigfile bs=1000000 count=1000
1000+0 records in
1000+0 records out
1000000000 bytes (1.0 GB) copied, 1.52658 s, 655 MB/s

real 0m1.529s
user 0m0.002s
sys 0m1.526s

"Slon daemon is running on the slave not the master", ummm I'm running the
slon daemon on all of my DB's (master/Slave, QuerySlave1, QuerySlave2)

 slon $CLS_CLUSTER -f /data/pgsql/slon.conf  "dbname=$ADMCLSDB
user=$SUPERUSER host=$SLAVEHOST" 2>&1 > /data/logs/slon.log &

I'll give the sync_max_rowsize a check as well

Thanks again

Tory
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20140103/dc0ffbd0/attachment.htm