27 Jan
2018
27 Jan
'18
3:03 p.m.
On 27.01.2018 21:41, Fons Adriaensen wrote:
On Sat, Jan 27, 2018 at 07:42:17PM +0100, Filipe
Coelho wrote:
Are those systems the regular 32 or 64bit intel systems?
While the hit might be no so significant there (for < 20 clients), the
same is not true for ARM-based CPUs in my experience.
When doing developing for MOD, internal vs external clients made a real
difference.
We were able to push around 30 clients (internal) instead of just 15 or
less (external).
The difference was clearly visible on the DSP load.
FYI, everything on the MOD platform runs as internal client, except for
jack capture.
On 27.01.2018 16:53, Chris Caudle wrote:
The JACK internal clients API disagrees with you ;)
Internal clients are faster to run, since they dont require context
switches between different processes.
They're harder to control externally though.
That's a bit too simple. They
will save a context switch only
if the previous or next client is internal as well.
And anyway, context switches are quite fast. I routinely run
systems with something between 15 and 20 Jack clients, the
overhead is absolutely insignificant. 3. JACK
"mixer" -> JACK DSP plugin -> JACK out (hw:0,0)
Rather than a
plugin, you will likely find it easier to develop a stand
along jack application. The jack design is not really made for having
plugins in the server.