How to give wwise more CPU bandwidth

Question

I'm an engineer working on a mobile VR (android) game that uses Wwise as its audio middleware.

When we use resonance audio rooms we almost always get voice starvation errors. A quick look at the profiler makes it seem like Wwise is being cpu bound, however we are not cpu bound generally, so i was wondering if we coudl somehow give wwise more access to the CPU to avoid this voice starvation error. I've looked through the settings and the optimization documentation and I've seen a ton of information about how to give wwise more memory, but nothing on how to give wwise more cpu/thread priority.

 

If this is not possible, suggestions on how to lower the (seemingly) excessive cost of resonance audio rooms would also be appreciated. I have tried having it 'tick' (push the values to wwise) on a slower timestep, which seems to help somewhat but not enough to solve this problem.