Simulating Internet Lag

2 Windows 2003 Servers SP1 Updated fully with SQL 2005 Beta 2

We are testing out the replication features in SQL 2005 (since they are supposedly improved from 2000) and we have hooked up the two databases to replicate to each other when changes are made to eithier one. Since these databases will be on the internet (Between German and US offices) the boss wants to replicate internet lag. We are looking about an average of 160-170ms lag (source ) between this office and Germany so I was wondering how we could replicate this on our network between 2 Windows 2003 Servers.

I have been playing with the following MS Paramaters:

- TCPWindowSize
- MaxMTU
- DefaultRcvWindow
- DefaultTTL
- DefaultMSS

with not much sucess.

Any ideas?

Could try using ping with the -t and -l switches on. Set it for maximum buffer size and how ever long you want?

Quote:

---

Originally posted here by Nokia
Could try using ping with the -t and -l switches on. Set it for maximum buffer size and how ever long you want?

---

Actually did a version of this. A ping -f -l 1320 Ip address gives me just about the right amount of lag over the net. (to another one of our servers in the US) However, when I did add it to the registry, it didnt change anything over the local network. I suppose I could of entered it wrong, but was following the MS directions.

You may need to increase the packet size of your ICMP packet to notice it over a LAN. Especially if your WAN has less bandwidth than your LAN(which i suspect is the case?).

What type/speed LAN are you running.

You may also need to use the -t switch to keep the pings constant.

Have you taken a look at any stress testing tools?

I know foundstone has a couple...

FSMax v2.0
A scriptable, server stress testing tool.
Download this Tool Now Click here for more information.

» Blast v2.0
A small, quick TCP service stress test tool.
Download this Tool Now Click here for more

» UDPFlood v2.0
UDP packet sender utility.
Download this Tool Now Click here for more information.

http://www.foundstone.com/resources/stress_testing.htm

Using something like Blast... you can do a continued ping and modify the blast parameters to your liking to get the "lag" that you're looking for. Are you doing this in a lab environment? On one segment? Across routers? If routers, look into bandwidth management and tweak the settings... or setup a frame relay simulation with a smaller CIR, etc. Don't know how big of a "pipe" you are using for your testing...

just a couple of ideas for you since I don't know exactly what type of setup you're going for.

Phish: Just between a small test lab in our office here. Win2k3 Server ----- Hub ------ Win2k3 Server

Not much that can manage in between.

Ill check out the stress testing tools and see if that cant do something for us.

Missed Nokia's post: Running the servers on their own 10 mb hub. Old sucker. Yes, the LAN is faster than the WAN. (1.5mb down 800k up)