September 29, 2009 at 3:06 am
Just trying to gather other people's views. Has anyone seen setting this on the logreader turn out to give negative performance?
I'm about to set off a job that will lead to 20 million inserts travelling up our 8mb line over a VPN and I wander whether I should set this. But if it ends up making it slower I'll be in trouble as I have a 6 hour gap to get the data up.
September 30, 2009 at 2:39 am
I did a test of sending 500000 records up the line. With maxcmdsintran set to 100000 so 5 transactions it took 17:57. With 1 transaction of 500000 it took 17 minutes, and the cmds/sec was 4 times as much.......So based on that I don't see the point!
September 30, 2009 at 3:42 am
If you set a large value for maxcmdsintran, and you have a network glitch, you have a potentially large number of commands to roll back and then resend.
You also have a large number of rows on the subscriber that are locked at any one time. If there is any activity on the subscriber, then this could be an issue.
For unreliable links or busy subscribers, you can potentially get better throughput with a smaller value. If your link is rock solid and the subscriber is not being used at the time, then this isn't an issue.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply