3 ms·
I have to say I am really appreciating the amount of conversation that arose here. My reading of this thread so far leaves me with: > AOT may be bad for real t
by bob1029 4y ago
I have to say I am really appreciating the amount of conversation that arose here. My reading of this thread so far leaves me with:
> AOT may be bad for real time audio due to compile-time assumptions and other heuristics that are limited by the lack of run-time history.
> JIT is probably bad for real time audio, unless you take special precautions to pre-condition the execution context with a workload that approximate the live one.
How does this sound?
- SemanticStrengh 4y agoThis sounds like we don't know how to sound.
- withinboredom 4y agoIf you are doing anything realtime, it's also going to depend on your hardware as much as your software. The real answer, is it depends and it's all tradeoffs. There's no "right" answer, but generally, you want things to be predictable (something that AOT gets you), but if your performance budget gives you the ability to stop the world and JIT (because hardware), then that's ok too.