Re: [tbench regression fixes]: digging out smelly deadmen.

Evgeniy Polyakov
2008-10-29T09:14:21Z

Hi.

Cooled down? Let's start over the sched vs network fight.

On Tue, Oct 28, 2008 at 11:37:41AM +0100, Ingo Molnar (mingo@elte.hu) wrote:
> What's your gut feeling, is that remaining small regression scheduler
> or networking related?
>
> i'm cutting the ball in half and i'm passing over one half of it to
> the networking folks, because your numbers show _huge_ sensitivity in
> this workload, depending on networking settings:

Sorry for interrupting your conversation, Ingo, but before throwing
a stone one should be clear himself, doesn't it? When you asked to
test -tip tree and it was showed it regressed about 20 MB/s in my
test against the last tweaks you suggested, -tip still was merged and no
work on this issue was performed. Now previous tweaks (nohrticks and
nobalalance, and although hrticks are now disabled, performance did not
return to the vanilla .27 with tweaks) do not help anymore, so
apparently there is additional problem.

So for the reference:
vanilla 27 : 347.222
no TSO/GSO : 357.331
no hrticks : 382.983
no balance : 389.802
4403b4 commit : 361.184
dirty_ratio-50 : 361.086
no-sched-tweaks : 361.367

So scheduler _does_ regress even right now when this thread is being
discussed.

Now let's return to the network. Ilpo Järvinen showed a nasty modulo
operation in the fast path which David thinks on how to resolve it, but
it happend that this change was introduced back in 2005, and although
some naive change allows to increase performance upto 370 MB/s, i.e. it
gained us 2.5%, this was never accounted in previous changes.

So, probably, if we revert -tip merge to vanilla .27, add nohrtick patch
and nobalance tweak _only_, and apply naive TSO patch we could bring
system to 400 MB/s. Note, that .22 has 479.82 and .23 454.36 MB/s.

--
Evgeniy Polyakov