From: "Lenar Lõhmus" <lenar@city.ee>
To: Klaus Schulz <Klaus.Schulz@web.de>
Cc: ck@vds.kolivas.org, linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: ck vs. cfs : realtime audio performance
Date: Tue, 31 Jul 2007 15:54:41 +0300 [thread overview]
Message-ID: <46AF3111.7090206@city.ee> (raw)
In-Reply-To: <1185886161.7397.11.camel@klaus-laptop>
Cc'd to LKML & Ingo.
L.
Klaus Schulz wrote:
> Hi there.
>
>
>
>
> Am Dienstag, den 31.07.2007, 10:26 +0200 schrieb Klaus Schulz:
>
>> Hi folks.
>>
>> I am currently testing the 2.6.22.1 cfs-rt9 vs. ck1 on my rather pure
>> realtime high-end-audio setup. (NO X, just a terminal, streaming .wav.
>> I am using my own written player and brutefir as the audio engine.)
>> Comment: This is not a standard (amarok or xmms setup), all buffers in
>> the chain are very small. Any problem will immidetialy end up in xruns.
>> The sounddriver, HW (pci-bus etc.) are tweaked accordingly
>>
>> Until now ck1 on 2.6.22 is giving me better results (less audible
>> distortions) and runs extremely stable compared to cfs.
>> Under ck I ran my player with schedtool -R -p 98, which was better than
>> running it e.g. with nice -20
>> Both setups under cfs were giving me worse results than ck.
>> With CFS I also experienced XRUNS from time to time, what never happened
>> with ck.
>>
>> However:
>>
>> When looking at the latest performance statistics cfs vs. ck which are
>> spread around here, I am wondering, what might cause the differences.
>>
>> With ck I tweaked the rr_interval to 6 and was running at 10000Hz,
>> which caused obvious improvements.
>>
>> These options I do not have with CFS.
>>
>> I am wondering if sched_granularity_ns should be touched when using cfs.
>> I googled somewhere that bringing it down to e.g. 250000 instead of
>> 4000000 would smoothen the audio playback. I havn't tried it yet. I am
>> wondering if this tweak is still applicable.
>>
>
>
>
> I did test now decreasing the sched_granularity_ns to 250000.
> There is still a clearly audible difference comparing ck and cfs.
> ck Ídelivers cristal clear sound. With cfs I still get quite some
> distortions.
>
> Any hints how to improve the situtation are welcome.
>
>
>
>
>> I'd be happy to get a hint on how to tweak the system parameters best to
>> give cfs a fair chance. I am also wondering how the timer freqency could
>> by increased under a cfs-patched kernel.
>>
>> Info: dynamic ticks and IRQ balancing are off for the time being.
>> /proc/sys/dev/rtc is set to 4096 (gave me best results)
>> ( I don't have a clue how all the (rtc)-timers in the OS interact,
>> To me it is just a trial and error exercise to figure out which
>> setup sounds best)
>>
>> THX for your advise.
>>
>> Cheers
>> \Klaus
>>
>
>
> Cheers
> \Klaus
>
>
> _______________________________________________
> http://ck.kolivas.org/faqs/replying-to-mailing-list.txt
> ck mailing list - mailto: ck@vds.kolivas.org
> http://vds.kolivas.org/mailman/listinfo/ck
>
next parent reply other threads:[~2007-07-31 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1185870355.7933.55.camel@klaus-laptop>
[not found] ` <1185886161.7397.11.camel@klaus-laptop>
2007-07-31 12:54 ` Lenar Lõhmus [this message]
2007-08-01 6:31 ` ck vs. cfs : realtime audio performance Ingo Molnar
2007-08-02 6:27 ` Carlo Florendo
2007-08-02 19:26 ` Ingo Molnar
2007-08-02 7:57 Klaus Schulz
2007-08-02 9:06 ` Carlo Florendo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46AF3111.7090206@city.ee \
--to=lenar@city.ee \
--cc=Klaus.Schulz@web.de \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox