From: Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Guenter Roeck <groeck-gvzKVTG1yJJBDgjK7y7TUQ@public.gmane.org>,
"Eric W. Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>,
Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org>,
Tejun Heo <htejun-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Serge E. Ha
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: Performance of netns with sysfs
Date: Thu, 15 Jan 2009 12:57:28 -0800 [thread overview]
Message-ID: <87ocy8thhj.fsf@caffeine.danplanet.com> (raw)
There has been some discussion lately about network namespaces and the
interaction with sysfs. With the introduction of Guenter's ipcgroup
patches, there was also the question of how feasible it is to create
thousands of network namespaces. So, I decided to see if I could even
create thousands of veth pairs, and if so move them into thousands of
network namespaces. I was pleased to see that the system didn't fall
over, but found that the process slowed significantly with higher
numbers if sysfs was enabled. I thought it would be prudent to post
some numbers.
I first tested creating 1000 and 2500 veth pairs, attaching one side
to a bridge with and without sysfs. Next I created 2500 network
namespaces, along with 2500 veth pairs. One side of each pair was
attached to a bridge and the other was moved into the namespace. The
results are:
1000 veth pairs: 8x slower with CONFIG_SYSFS
2500 veth pairs 4.5x slower
2500 netns, veth pairs: 6x slower
The tests were done with hal disabled, attaching every third veth
device to a different bridge (to overcome the limit of 1023 taps per
bridge).
--
Dan Smith
IBM Linux Technology Center
email: danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
next reply other threads:[~2009-01-15 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 20:57 Dan Smith [this message]
[not found] ` <87ocy8thhj.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2009-01-15 21:37 ` Performance of netns with sysfs Guenter Roeck
2009-01-15 21:48 ` Dan Smith
2009-01-16 4:35 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ocy8thhj.fsf@caffeine.danplanet.com \
--to=danms-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=daniel.lezcano-GANU6spQydw@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=groeck-gvzKVTG1yJJBDgjK7y7TUQ@public.gmane.org \
--cc=htejun-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.