I want to use LRP to simulate a low-bandwidth connection:
Application Database
| |
|Crossover |Crossover
| |
LRP---------------------LRP
Crossover
I'm thinking of enabling fair queuing and establishing a single traffic
type. There's a couple of catches, though:
I want to limit bandwidth available. Limiting bandwidth looks like it can
be done pretty easily, after perusing the EigerSteinBETA2 scripts. But I'm
not sure that establishing a single queue is effectively going to put all
traffic into that queue. I'm also not sure if the queue is used on both
traffic directions or only on one -- wouldn't want to accidentally double
my restriction... Is there a way to make the queue unidirectional?
I want to introduce latency in a controlled manner. The link I'm going to
simulate is ATM and currently provides about 200 ms latency (not bad for
Santa Clara to London, huh?). I haven't got the slightest idea how to
control latency. The queue buffering will certainly introduce a component,
but I need that to be in addition to the latency of a real transoceanic
cable because there will be buffering in the real application as well.
For the curious, this is a customer who wrote their app assuming global
support could be done from a single datacenter and has since discovered
that they need a regional presence for certain functions to work. However
since all traffic passes through the database and needs to be near real
time... when all roads lead to Rome you can't have two Romes.
--
Jack Coates
Monkeynoodle: It's what's for dinner!
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
