Date: Tue, 6 Nov 2007 21:36:24 -0800 From: "Josh Carroll" <josh.carroll@gmail.com> To: "Jeff Roberson" <jroberson@chesapeake.net> Cc: freebsd-performance@freebsd.org Subject: Re: ULE vs. 4BSD in RELENG_7 Message-ID: <8cb6106e0711062136r18ca8e67sbdb4d4372e10e086@mail.gmail.com> In-Reply-To: <20071106171059.M544@10.0.0.1> References: <8cb6106e0710230902x4edf2c8eu2d912d5de1f5d4a2@mail.gmail.com> <20071103121921.M544@10.0.0.1> <8cb6106e0711031416l4183e2beueb87fade0d56f504@mail.gmail.com> <20071103133711.Q544@10.0.0.1> <8cb6106e0711032221i2ecf1d59ge82f368d4162a827@mail.gmail.com> <20071104122546.S544@10.0.0.1> <8cb6106e0711041243s37ef92e3i9c5c79827f547dbb@mail.gmail.com> <20071104151722.M544@10.0.0.1> <8cb6106e0711050141g674a7733h53f7e6a20e75ad07@mail.gmail.com> <20071106171059.M544@10.0.0.1>
next in thread | previous in thread | raw e-mail | index | archive | help
> That's expected due to the fuzzy rounding of 128 / 10, etc. Can you set > slice_min and slice both equal to 7 and see if the numbers come out > better than without the patch but with a slice value of 7? Basically I'm > trying to isolate the effects of the different slice handling in this > patch from the other changes. Here are the results. Looks like setting slice_min and slice to 7 degraded performance for all work loads. Should I try any other settings for slice and slice_min? ffmpeg: 1:39.91 sysbench (4, 8, 12, 16 threads respectively): 2013.78 2157.6 2175.91 2184.16 And buildworld time: 14m7.517s Thanks! Josh
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8cb6106e0711062136r18ca8e67sbdb4d4372e10e086>