Log compression for replication ??
As I mentioned a few days ago, replication traffic has spiked up on our network. It was because of periodic purges that were running. This is becoming a big issue in my company that we are eating up bandwidth because online users get bloced. Is there any way to have Informix compress the logs before they are shipped out to the secondary ? I've looked through the manuals and havent found anything and was surprised. This might be a good enhancement to suggest to the Informix development group. TIA, Jack
Oh no. I think i havent given you the complete picture. The backbone gets used for a lot of stuff. There are many other applications that use the back bone apart from Informix users. Connections to the primary are working fine. There are no problems with that. But we have other servers here in the head office which are accessed using the same back bone by different users. When the purge runs and the network gets clogged, these users are the ones which have a problem. So seperating replicaton traffic from user traffic is really not my goal. I only want to minimize replication traffic any way I can. "Madison Pruet" <mpruet@comcast.net> wrote in message news:Gp5%a.149060$o%2.64395@sccrnsc02... > Jack, > > You should be able to separate the replication traffic from the user traffic > by setting up separate ports (listener threads), one for the HDR traffic > and the other for the user apps. > > I'm a bit puzzled by this, however. If the network bandwidth is the cause > of the problem, then I would expect only connections to the secondary to be > a problem, not the primary. Could it be that the real problem is that the > users are locking because the purge program is not committing often enough > and thus causing users to be in a wait state on rows to be deleted? > > > "Jack A" <hrehal@yahoo.com> wrote in message > news:5b83c3e5548b78f5201f76f39bc79d8d@news.teranews.com... > > As I mentioned a few days ago, replication traffic has spiked up on our > > network. It was because of periodic purges that were running. This is > > becoming a big issue in my company that we are eating up bandwidth because > > online users get bloced. Is there any way to have Informix compress the > logs > > before they are shipped out to the secondary ? I've looked through the > > manuals and havent found anything and was surprised. > > > > This might be a good enhancement to suggest to the Informix development > > group. > > > > TIA, > > Jack > > > > > >
Jack, You should be able to separate the replication traffic from the user traffic by setting up separate ports (listener threads), one for the HDR traffic and the other for the user apps. I'm a bit puzzled by this, however. If the network bandwidth is the cause of the problem, then I would expect only connections to the secondary to be a problem, not the primary. Could it be that the real problem is that the users are locking because the purge program is not committing often enough and thus causing users to be in a wait state on rows to be deleted? "Jack A" <hrehal@yahoo.com> wrote in message news:5b83c3e5548b78f5201f76f39bc79d8d@news.teranews.com... > As I mentioned a few days ago, replication traffic has spiked up on our > network. It was because of periodic purges that were running. This is > becoming a big issue in my company that we are eating up bandwidth because > online users get bloced. Is there any way to have Informix compress the logs > before they are shipped out to the secondary ? I've looked through the > manuals and havent found anything and was surprised. > > This might be a good enhancement to suggest to the Informix development > group. > > TIA, > Jack > >