Re: Low Latency vs. Real Time Kernel - actual latencies ?
- To: Fernando Lopez-Lezcano <nando@xxxxxxxxxxxxxxxxxx>
- Subject: Re: Low Latency vs. Real Time Kernel - actual latencies ?
- From: Brian Monroe <briancmonroe@xxxxxxxxx>
- Date: Tue, 21 Feb 2012 22:20:16 -0800
- Authentication-results: mr.google.com; spf=pass (google.com: domain of briancmonroe@xxxxxxxxx designates 10.68.237.40 as permitted sender) smtp.mail=briancmonroe@xxxxxxxxx; dkim=pass header.i=briancmonroe@xxxxxxxxx
- Cc: music@xxxxxxxxxxxxxxxxxxxxxxx
- Delivered-to: music@xxxxxxxxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yxyLhnCHW/jFXjTCjYFEBhPHIpHPKEogF2q8094pqlw=; b=Kv+DyO1FGXK7XOfGQnXI4IqUm28D0R7YGL4jesTFty0a3Rxbm+IPsOe1KDASZzXWpM S/I8o4TtszgFgBuc8TihOYHMjJks2ZMV6TSx5pObCMW6rwUMX133NZDy6SNNoRctvuQR cwrZH3farqnhYC3I4w8+kJM8rMHVb8YYeZ+qU=
- In-reply-to: <4F3D4CD0.5040909@localhost>
- References: <CALwM5Wsd4XXbAw+hBPrtzE-mC7mTe9_xa1D3RTzWdQqEocXoRg@mail.gmail.com> <CALwM5Ws+T=4VL9zuiT9E3-+3UCbqBM5D1YC=Rp774dY2EMfnhw@mail.gmail.com> <CALwM5Wt8CfPYXWAb-vXboWzHAqo=DauuCSnJx3C02cxFBhmFVQ@mail.gmail.com> <CALwM5WtNTdUTrr7eShD78tGkfKF8CvwJS==rCSBp5xitKZO_1Q@mail.gmail.com> <CALwM5WtX8eScc9LWRwPOEkL7b_vwa_rWKqJZ080qnrAiVwkAwg@mail.gmail.com> <CALwM5Wu_==L-rUY4MCRVuNVSY8MzSdwqJZD3ivteBwZQMvVBxg@mail.gmail.com> <4F3AC242.8070109@gmail.com> <CALwM5WtSZVMSf_O=5U=WzSZnZ97+8cMV_Wsidb+2EoyBRQRZQA@mail.gmail.com> <4F3CF7B4.8030106@iinet.net.au> <4F3D4CD0.5040909@localhost>
I didn't have time tonight to get tests on all the kernels under load, but here are the results, relatively load free.
I need to write a short python program to put the systems under duress. Hopefully I'll have time tommorrow to work on it and I can have the rest of the results in.
PS:I'm attaching some results from an RT kernel on a debian system below that they used while the box was recieving flood ping from an external source and repeated loops of hackbench 25 and ls -Ral /.
# cyclictest -a -t -n -p99 -i100 -d50
560.44 586.11 606.12 211/1160 3727
T: 0 (18617) P:99 I:100 C:1011846111 Min: 2 Act: 4 Avg: 5 Max: 39
T: 1 (18618) P:98 I:150 C: 708641019 Min: 2 Act: 5 Avg: 11 Max: 57
On Thu, Feb 16, 2012 at 10:37 AM, Fernando Lopez-Lezcano
<nando@xxxxxxxxxxxxxxxxxx> wrote:
On 02/16/2012 04:33 AM, David Timms wrote:
On 15/02/12 16:49, Brian Monroe wrote:
On Tue, Feb 14, 2012 at 12:21 PM, Brendan Jones
<brendan.jones.it@xxxxxxxxx>wrote:
Latency times are really relative things based on many factors. Have you
been getting better latency times than ta
yeah.
I would be good to see real numbers associated with claims like the
above; also how it is measured..
Cyclictest is widely used for measuring latencies:
https://rt.wiki.kernel.org/articles/c/y/c/Cyclictest.html
Also, indicate those various kernel patches and or options they use or
have tested.
The rt patches for the latest kernels (3.2 at this point) are here:
http://www.kernel.org/pub/linux/kernel/projects/rt/3.2/
This is pretty much all I add to the rt patched kernels for Fedora (with the proper configuration options, of course, I'm attaching the extra options I'm currently using). To get the best performance in the Jack world you need to tune the irq kernel thread priorities, that is usually done using rtirq (http://www.rncbc.org/jack/#rtirq), and of course jackd should run with the proper rt priority as well.
-- Fernando
_______________________________________________
music mailing list
music@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/music
Attachment:
latency
Description: Binary data
_______________________________________________
music mailing list
music@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/music
[Fedora Legacy Announce]
[Fedora Extras]
[Home]
[Kernel]
[Fedora Legacy]
[Fedora Desktop]
[Fedora Directory]
[PAM]
[Red Hat Development]
[Red Hat 9 Bible]
[Red Hat 9]
[Big List of Linux Books]
[Gimp]
[Yosemite News]
[Yosemite Camping]