[Planetlab-users] Re: [Planetlab-devel] Network virtualization

[Daniel Lezcano]

Daniel Lezcano wrote:

>> The evaluation strategy used is to compare the effective performance
>> of containers running with their own copy of the protocol stack with
>> that of processes on native Linux. Any significant deviation should
>> imply a major overhead in the implementation. Specifically, we run
>> the following steps:
>>
>> (i) We start with 1 container pushing out or routing data at full
>> throttle and progressively increase the number of containers,
>> measuring the overall throughput, CPU utilization and jitter. This is
>> not a good microbenchmark because the length of a time slice allows
>> containers to send out a few dozen packets in every burst - meaning
>> that packet sends are not interleaved, and there is no added
>> contention in the stack. But it's a good macrobenchmark, because this
>> is what we'd like to do in the context of PlanetLab (run many slices
>> at once). The only additional thing it brings into play is the
>> context-switch overhead.

You previously said the test was between 2 machines. Does the test 
measure the throughput between these 2 hosts with one peer inside the 
container or outside the container ?

When a container is spawn, does it have a new network configuration set, 
I mean a etun device with each extremities in both namespaces (parent 
and child) and with an IP address set ?

My major concern is to know what is the impact having one application 
running inside a container communicating with the outside world and with 
the other containers in the same host.


Regards.

	-- Daniel