[Tremor] "Bursty-ness"

[Darren Gibbs]

We're evaluating tremor for use in an upcoming product, and after doing
some performance analysis, have discovered that it is surprisingly
bursty.  Reducing the number of samples requested helped, but still...
the time required to return a block of 128 samples can differ by a
factor of 100.  Is this typical/expected?  Has anyone experimented with
strategies for smoothing out the decode time?

thanks,

darren