Date: Wed, 4 Jan 2006 07:59:26 +0100 From: Oliver Brandmueller <ob@e-Gitt.NET> To: freebsd-isp@freebsd.org Subject: Re: FreeBSD +NFS + mail services Message-ID: <20060104065926.GA99739@e-Gitt.NET> In-Reply-To: <cone.1136336702.793300.48688.1000@zoraida.natserv.net> References: <cone.1136336702.793300.48688.1000@zoraida.natserv.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--a8Wt8u1KmwUX3Y2C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello. On Tue, Jan 03, 2006 at 08:05:02PM -0500, Francisco Reyes wrote: > Looking for any links/comments/info on performance settings for a FreeBSD= =20 > mail setup using NFS. >=20 > In particular how does the client decides how many client nfs programs to= =20 > run? I noticed that 2 machines today were both using 22 client=20 > connections each. Is that a hard limit in the FreeBSD nfs client? Look at the sysctl vfs.nfs -> vfs.nfs.iodmin: 4 vfs.nfs.iodmax: 20 In FreeBSD 6 you'll also find: vfs.nfs.iodmaxidle: 120 Should be pretty self explanatory. How many you actually need depends=20 very much on your configuration and how busy your servers are, how many=20 mailboxes, how many mails per minute. Also it depends if your clients=20 access e-Mails via IMAP or by POP3 (or whatever method apart from that).=20 Especially IMAP can be very resource hungry. So I cannot really give you hints on actual values, because they very much depend on your setup. You should also play around with NFS read and write data sizes, the bufpackets and such values until they best match your setup with respect of speed of clients and server and the network and again, how busy your setup is at the moment. Just run different benchmarks in your test area or before going to production. And while being in prod you could take the chance to make performance monitoring on all the machines and carefully change different variables (i.e. use of rdirplus, different buffer values). Also you could try to use Jumbo Frames on your NFS backbone, given it is GigE only and _all_ of your hardware and software (switches, every single NIC, every single OS/driver involved) really supports this. > Our current NFS server is a 5.4 machine and a new one coming online soon= =20 > will be 6.X stable. Client machines are 5.4 I just migrated our NFS server(s) from 5.4 to 6.0 - our clients are=20 mainly still 5-STABLE, only few 6-STABLE clients. I saw a few NFS=20 locking problems (lockd starting to spin) with the server while it was=20 still RELENG_5, especially after stating with RELENG_6 clients. This was=20 clearly load dependant (started usually on busy days when the backup was=20 running into daytime). I haven't seen this yet with RELENG_6 servers,=20 but the migration was just one week ago and the backup scheme had been=20 changed also to avoid the problem, so I'm not completely sure here. - Oliver --=20 | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | --a8Wt8u1KmwUX3Y2C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDu3JOiqtMdzjafykRAt1QAKCPpxNbO13i68sknoF0Iml019RQbQCfdcg3 7LJhkB6JlD/4yQOkT3yfi58= =T1/Z -----END PGP SIGNATURE----- --a8Wt8u1KmwUX3Y2C--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060104065926.GA99739>