I look forward to seeing JeffS's results. Other tests I have done with multiple connections between multiple zones also showed no overhead. But those tests did not include large numbers of connection creations per second.

But there really isn't any extra code if the packet is traveling between zones, so, unless there's a bug in the network setup/teardown code that causes a performance hit, we really should begin to investigate network-configuration issues and non-network issues. That explains my earlier desire for the zonecfg info.

Jeff Savit wrote:
When I get a chance, I'll reproduce many connections/s (instead of bytes/s)
across zones, compared to intra-zone, using Apache's 'ab' tool, and report
what I get.  -- Jeff

Gino Ruopolo wrote:
I would not read too much into those values, but I think that it is
safe to conclude that there is little difference in network performance
among those situations.  The two situations you have described are (4)
and (5).

In my setup I have about 1000 connection/s, not a single connection.

Is it possible that establishing a new connection between 2 processes in
2 different zones costs about 18% more than the same processes in the
same zones?

If we can rule out network performance, we must look elsewhere.  Would
you send the zonecfg info for the two zones you have been using?

Full zone, single ip, nothing else.  Sure I can send you the config
tomorrow if you like but you'll not find anything interesting :(

Also, how many zones are running on this system?

Only the zones I'm writing about.

tnx, gino

This message posted from opensolaris.org _______________________________________________ zones-discuss mailing
list zones-discuss@opensolaris.org


_______________________________________________ zones-discuss mailing list zones-discuss@opensolaris.org

Jeff VICTOR              Sun Microsystems            jeff.victor @ sun.com
OS Ambassador            Sr. Technical Specialist
Solaris 10 Zones FAQ:    http://www.opensolaris.org/os/community/zones/faq
zones-discuss mailing list

Reply via email to