1So, you want vsftpd to go quickly?
2
3Here are some random assorted performance tips.
4
51) vsftpd thrives because of its lightweight RSS and vm usage. If you run
6a glibc based system (e.g. RedHat 5+), look in /etc/nsswitch.conf, and
7if possible, disable the "nis" and "nisplus" options for "passwd", "shadow"
8and "group". This prevents unneeded runtime libraries being added into
9the vsftpd virtual memory space.
10
112) vsftpd will attempt to save CPU power by using sendfile() on capable
12operating systems. Currently, Linux 2.2+ and FreeBSD 3.0+ use sendfile().
13Consider running on these excellent operating systems.
14
153) Irritated by vsftpd using _two_ processes per connection? Don't be, it's
16a very secure architecture. However, if you run Linux 2.4+, or Linux 2.2.19+, a
17"one process" security model is possible thanks to nifty security features.
18See the vsftpd.conf man page.
19
204) Avoid large directories (e.g. thousands of entries) if possible. Many
21filesystems do not handle such cases efficiently at all. Preparing large
22directory listings will require vsftpd to use moderate amounts of memory
23and CPU. If you _must_ have large directories, consider either making them
24unreadable, or use a filesystem which copes well with large directories such
25as reiserfs.
26
27