Re: CURRENT as gateway on not-so-fast hardware: where is a
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigA13AA7BCE4240602815D84F4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 20.08.12 10:32, Doug Barton wrote:
> On 08/15/2012 03:18, Alexander Motin wrote:
>>
>> It is quite pointless to speculate without real info like mentioned
>> above KTR_SCHED traces.
>=20
> I'm sorry, you're quite wrong about that. In the cases I mentioned, and=
> in about 2 out of 3 of the cases where users reported problems and I
> suggested that they try 4BSD, the results were clear. This obviously
> points out that there is a serious problem with ULE, and if I were the
> one who was responsible for that code I would be looking at ways of
> helping users figure out where the problems are. But that's just me.
>=20
>> Main thing I've learned about schedulers, things
>> there never work as you expect. There are two many factors are relatio=
ns
>> to predict behavior in every case.
>=20
> In the web hosting case that I mentioned, I purposely kept every other
> factor consistent; and changed only s/ULE/4BSD/. The results were both
> clear and consistent.
>=20
Can you please prove that with some actual numbers? I seem to recall you
posted something not too long ago but i was unable to find that right now=
=2E
Also can you tell us what you ran and how. I would really like to
reproduce this.
Thanks,
Florian
--------------enigA13AA7BCE4240602815D84F4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
iEYEARECAAYFAlAz/xQACgkQapo8P8lCvwmabACgr2kUZ62RJnd8pDTu9hHis8QQ
or0An3BkPQSuH6OAHuEfD+IzHw/xN4Sp
=mEa1
-----END PGP SIGNATURE-----
--------------enigA13AA7BCE4240602815D84F4--
討論串 (同標題文章)
完整討論串 (本文為第 35 之 35 篇)：