Kai Vehmanen wrote:
> The current ecasound (2.0.0) still uses threads, but much more sparingly
> than before. In a normal setup, you have four threads running:
> 1) engine thread (_highest_ priority)
> 2) MIDI-thread (high priority - running if MIDI used)
> 3) disk i/o thread (high priority - ... if -z:db specified)
> 4) ui-thread (low priority - ... if a frontend is used)
>
> ... one benefit of this simple approach is that it is relatively easy to
> identify the performance bottlenecks. But it's also true that this setup
> is not optimal for cpu-intensive tasks like complex dsp-networks. So this
> is clearly a compromise.
Why is this not optimal for complex dsp-networks ? Are you talking
about making use of multiple processors, or is there some more
fundamental issue ?
Jim
--
Jim Peters / __ | \ Aguazul
/ /| /| )| /| / )|| \
jim@aguazul. \ (_|(_|(_|(_| )(_|I / www.aguazul.
demon.co.uk \ ._) _/ / demon.co.uk
- [linux-audio-dev] Re: [alsa-devel] Re: laag... Paul Davis
- [linux-audio-dev] Re: [alsa-devel] Re: ... Abramo Bagnara
- Re: [linux-audio-dev] Re: [alsa-devel] Re: ... Jay Ts
- [linux-audio-dev] Re: [alsa-devel] Re: laaga, round... Kai Vehmanen
- [linux-audio-dev] Re: [alsa-devel] Re: laaga, r... Abramo Bagnara
- [linux-audio-dev] Re: [alsa-devel] Re: laag... Paul Davis
- [linux-audio-dev] Re: [alsa-devel] Re: ... Abramo Bagnara
- [linux-audio-dev] Re: laaga, round 2 Alexander Ehlert
- Re: [linux-audio-dev] Re: laaga, round 2 Paul Davis
- [linux-audio-dev] Re: laaga, round 2 Kai Vehmanen
- Re: [linux-audio-dev] Re: laaga, round ... Jim Peters
- Re: [linux-audio-dev] Re: laaga, round 2 Stefan Westerfeld
- [linux-audio-dev] Re: [alsa-devel] Re: laaga, round... Jim Peters
- [linux-audio-dev] Re: [alsa-devel] Re: laaga, r... Abramo Bagnara
- Re: [linux-audio-dev] laaga, round 2 Jay Ts
