Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 14 Aug 2012 14:09:25 -1000
From:      Doug Barton <dougb@FreeBSD.org>
To:        Adrian Chadd <adrian@freebsd.org>
Cc:        mav@FreeBSD.org, lev@freebsd.org, current@freebsd.org
Subject:   Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?
Message-ID:  <502AE8B5.9090106@FreeBSD.org>
In-Reply-To: <CAJ-Vmon86-FPs4%2BXXkQXAow1jW465pMM2Sj7ZHi_0_E9VYSFSA@mail.gmail.com>
References:  <157941699.20120815004542@serebryakov.spb.ru> <CAJ-Vmon86-FPs4%2BXXkQXAow1jW465pMM2Sj7ZHi_0_E9VYSFSA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 08/14/2012 12:20 PM, Adrian Chadd wrote:
> Hi,
> 
> Would you be willing to compile a kernel with KTR so you can capture
> some KTR scheduler dumps?
> 
> That way the scheduler peeps can feed this into schedgraph.py (and you
> can too!) to figure out what's going on.
> 
> Maybe things aren't being scheduled correctly and the added latency is
> killing performance?

You might also try switching to SCHED_ULE to see if it helps.

Although, in the last few months as mav has been converging the 2 I've
started to see the same problems I saw on my desktop systems previously
re-appear even using ULE. For example, if I'm watching an AVI with VLC
and start doing anything that generates a lot of interrupts (like moving
large quantities of data from one disk to another) the video and sound
start to skip. Also, various other desktop features (like menus, window
switching, etc.) start to take measurable time to happen, sometimes
seconds.

... and lest you think this is just a desktop problem, I've seen the
same scenario on 8.x systems used as web servers. With ULE they were
frequently getting into peak load situations that created what I called
"mini thundering herd" problems where they could never quite get caught
up. Whereas switching to 4BSD the same servers got into high-load
situations less often, and they recovered on their own in minutes.

Doug




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