LinuxDevCenter.com

oreilly.comSafari Books Online.Conferences.

We've expanded our Linux news coverage and improved our search! Search for all things Linux across O'Reilly!

Search
Search Tips

advertisement

Print Subscribe to Linux Subscribe to Newsletters
Linux & Unix > Excerpts >

Audio-latency test results (audio buffer 3 x 256 bytes)

Test results for:

  • Kernel: 2.2.10 patched, tuned
  • Kernel: 2.2.17 patched, tuned
  • Kernel: 2.4.0-test9, unpatched, untuned
  • Kernel: 2.4.0-test9, patched, untuned
  • Kernel: 2.4.0-test9, patched, tuned

Key to graphs

(Click here to open this key in a pop-up window for reference while viewing graphs)

  • The red reference line is the global audio buffer size; if this deadline is missed you will hear a sound drop-out.

  • The white line is the actual scheduling latency, the ideal would be the time it takes to play 1 audio fragment (fragment latency).

  • The green line is the time the CPU takes to execute an empty loop (which is calibrated at 80% of the fragment time).

    This is used to simulate heavy CPU computations during the audio play, a typical example could be a synthesizer which computes the waveform to play in realtime.

    Since the thread runs with SCHED_FIFO priority, if this time goes up, then the cause could be the DMA / PCI / ISA contention on the system bus, or busy kernel I/O routines.

  • The yellow reference line is the len of one audio fragment (ideally the white line should stay close to yellow line).

  • The white between +/-1ms is the % of time the total latency stays in the range between +/-1ms of the optimal latency.

  • The white between +/-2ms is the % of time the total latency stays in the range between +/-2ms of the optimal latency.

  • The green between +/-0.2ms is the % of time the CPU loop latency stays in the range between +/-0.2ms of the nominal CPU loop latency.

  • The green between +/-0.1ms is the % of time the CPU loop latency stays in the range between +/-0.1ms of the nominal CPU loop latency.

Kernel: 2.2.10 patched, tuned

X11 stress (2.2.10 patched, tuned)

X11 stress

/proc filesystem stress (2.2.10 patched, tuned)

proc filesystem stress.

Disk write stress (2.2.10 patched, tuned)

Disk-write stress

Disk copy stress (2.2.10 patched, tuned)

Disk copy stress

Disk read stress (2.2.10 patched, tuned)

Disk read stress

View other test results:

  • Kernel: 2.2.17 patched, tuned
  • Kernel: 2.4.0-test9, unpatched, untuned
  • Kernel: 2.4.0-test9, patched, untuned
  • Kernel: 2.4.0-test9, patched, tuned

Return to Achieving Low-Latency Response Times Under Linux

Pages: 1, 2, 3, 4, 5

Next Pagearrow




Tagged Articles

Be the first to post this article to del.icio.us

Recommended for You

Sponsored Resources

  • Inside Lightroom
Advertisement

Sponsored by:

Sign up today to receive special discounts,
product alerts, and news from O'Reilly.
Privacy Policy >
View Sample Newsletter >
  • Youtube
  • http://www.youtube.com/OreillyMedia
  • Twitter
  • Subscribe
  • View All RSS Feeds >
O'Reilly Media

800-889-8969 or 707-827-7019
Monday-Friday 7:30am-5pm PT
©2011, O'Reilly Media, Inc.
All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners.
  • About O'Reilly
  • Academic Solutions
  • Contacts
  • Customer Service
  • Careers
  • Press Room
  • Privacy Policy
  • Terms of Service
  • Writing for O'Reilly
  • Community
  • Authors
  • Forums
  • Membership
  • Newsletters
  • RSS Feeds
  • User Groups
  • More O'Reilly Sites
  • igniteshow.com
  • makerfaire.com
  • makezine.com
  • craftzine.com
  • labs.oreilly.com
  • Partner Sites
  • PayPal Developer Zone
  • O'Reilly Insights on Forbes.com