Hi,
I'm new to Slony so indepth knowledge lacks a little. I have set up a Slony
cluster (master and one subscriber). The master has lots of work to do on a
daily basis. Here some figures of the most heavy hit tables and what Slony did
in the period (12am to 12am). Figures are roughly the same on a daily basis.
relname | Insert | Update | Delete
-----------------------------------+---------+--------+---------
t01 | 266471 | 267357 | 0
t02 | 316085 | 33352 | 0
t03 | 334 | 0 | 0
t04 | 3112 | 0 | 0
t05 | 128794 | 160 | 0
t06 | 897 | 130857 | 0
t07 | 2111989 | 0 | 2024579
t08 | 16163 | 0 | 15929
t09 | 148653 | 0 | 147486
t10 | 2507 | 0 | 1975
t11 | 701656 | 0 | 695135
t12 | 328510 | 0 | 322875
t13 | 397709 | 0 | 383299
t14 | 61364 | 0 | 59752
sl_archive_counter | 0 | 0 | 0
sl_config_lock | 0 | 0 | 0
sl_confirm | 38292 | 0 | 38002
sl_event | 26625 | 0 | 17466
sl_listen | 0 | 0 | 0
sl_log_1 | 8569209 | 0 | 8543943
sl_log_2 | 0 | 0 | 0
sl_node | 0 | 0 | 0
sl_nodelock | 9 | 0 | 9
sl_path | 0 | 0 | 0
sl_registry | 0 | 330 | 0
sl_seqlog | 161004 | 0 | 52572
sl_sequence | 0 | 0 | 0
sl_set | 0 | 0 | 0
sl_setsync | 0 | 0 | 0
sl_subscribe | 0 | 0 | 0
sl_table | 0 | 0 | 0
sl_trigger | 0 | 0 | 0
I started the slon deamon processes with default settings. Now lagtime is
running up hill. I expirimented a little with group size, SYNC intervals but
that does not seem to help much. Slony now seems to hang in the
st_last_received_event_ts for long time. A select from sl_status:
-[ RECORD 1 ]-------------+---------------------------
st_origin | 1
st_received | 2
st_last_event | 714823
st_last_event_ts | 2008-01-25 12:31:07.917925
st_last_received | 694710
st_last_received_ts | 2008-01-25 11:06:19.889191
st_last_received_event_ts | 2008-01-24 02:08:35.640458
st_lag_num_events | 20113
st_lag_time | 1 day 10:22:33.398227
-[ RECORD 2 ]-------------+---------------------------
st_origin | 1
st_received | 3
st_last_event | 714823
st_last_event_ts | 2008-01-25 12:31:07.917925
st_last_received | 714822
st_last_received_ts | 2008-01-25 12:31:07.874295
st_last_received_event_ts | 2008-01-25 12:31:02.911062
st_lag_num_events | 1
st_lag_time | 00:00:06.127623
Node 3 has no replication yet (but should have after this weekend)
Current count of the slony tables in the master:
Tabelnaam | count
---------------------+----------
sl_archive_counter | 1
sl_config_lock | 0
sl_confirm | 636
sl_event | 20108
sl_listen | 11
sl_log_1 | 18272903
sl_log_2 | 0
sl_node | 3
sl_nodelock | 4
sl_path | 6
sl_registry | 4
sl_seqlog | 238392
sl_sequence | 11
sl_set | 4
sl_setsync | 0
sl_subscribe | 4
sl_table | 46
sl_trigger | 0
sl_status | 2
My question is if anyone can help me out with tips on how to improve
replication speed. Or do I have to live with the current speed. When running
the batch proces with no lag delay at start Slony got behind roughly 50 minutes
an hour.
Jaco
This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be copied,
disclosed to, retained or used by, any other party. If you are not an intended
recipient then please promptly delete this e-mail and any attachment and all
copies and inform the sender. Thank you.
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
