Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 23 May 2005 14:36:10 -0700
From:      Kris Kennaway <kris@obsecurity.org>
To:        Kris Kennaway <kris@obsecurity.org>
Cc:        Mike Jakubik <mikej@rogers.com>, Matthias Buelow <mkb@incubus.de>, freebsd-stable@freebsd.org
Subject:   Re: Performance of 4.x vs 5.x (Re: Lifetime of FreeBSD branches)
Message-ID:  <20050523213609.GA47212@xor.obsecurity.org>
In-Reply-To: <20050523213155.GA46718@xor.obsecurity.org>
References:  <3248.172.16.0.199.1116876092.squirrel@172.16.0.1> <20050523195123.GA13810@xor.obsecurity.org> <3482.172.16.0.199.1116882013.squirrel@172.16.0.1> <20050523211307.GA36552@xor.obsecurity.org> <42924949.1070902@incubus.de> <20050523213155.GA46718@xor.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--ZGiS0Q5IWpPtfppv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, May 23, 2005 at 02:31:55PM -0700, Kris Kennaway wrote:
> On Mon, May 23, 2005 at 11:21:13PM +0200, Matthias Buelow wrote:
> > Kris Kennaway wrote:
> >=20
> > > One thing that probably confuses and misleads a lot of people is when
> > > they build world or a kernel and notice that it's taking much longer
> > > than it did under 4.x, so they assume this means that 5.x is slower
> > > than 4.x.  It doesn't.  What it means is that 5.x and 4.x have
> > > different C compilers, and gcc 3.x is much slower at compiling code
> > > than gcc 2.x.  You have to be very careful to draw conclusions based
> > > on subjective assessments like this.
> >=20
> > Another thing might be that interactive response time seems to be worse.
> >  While I (or rather ports) unpack the firefox/thunderbird source, the
> > machine is pretty much bogged down (mouse cursor jumps around, audio
> > stutters...).  Haven't seen that on FreeBSD since the 386 days.
>=20
> I don't run FreeBSD on my desktop machines so I haven't seen this
> myself.  One obvious guess is that it's due to VFS being under Giant,
> which causes lots of contention with other subsystems that also
> require Giant, and therefore introduces latency.  If so, you'd see a
> substantial performance improvement on 6.0 with debug.mpsafevfs=3D1.
> This option isn't yet ready for production use (especially on SMP
> machines) since it still contains bugs, but it would be interesting if
> someone who sees this problem could test it on 6.0.

Also try defining PREEMPTION in your kernel on 5.x and above (if you
are running i386 or amd64).  There have been very occasional reports
of panics with this option enabled (although I use it everywhere and
have not seen problems on my heavily loaded machines), but interactive
response should be much better.

Kris

--ZGiS0Q5IWpPtfppv
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQFCkkzIWry0BWjoQKURAkimAJ963b0FzR02Mhu9XWu0/v3NyqkBIwCdGBX/
ouRkPovKNRUb7kFrGsFsOn4=
=C80q
-----END PGP SIGNATURE-----

--ZGiS0Q5IWpPtfppv--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050523213609.GA47212>