Oliver Woodman 37e6946cd9 Finally - Remove Sample, fix GC churn + inefficient memory usage. ...

Use of Sample objects was inefficient for several reasons:

- Lots of objects (1 per sample, obviously).
- When switching up bitrates, there was a tendency for all Sample
  instances to need to expand, which effectively led to our whole
  media buffer being GC'd as each Sample discarded its byte[] to
  obtain a larger one.
- When a keyframe was encountered, the Sample would typically need
  to expand to accommodate it. Over time, this would lead to a
  gradual increase in the population of Samples that were sized to
  accommodate keyframes. These Sample instances were then typically
  underutilized whenever recycled to hold a non-keyframe, leading
  to inefficient memory usage.

This CL introduces RollingBuffer, which tightly packs pending sample
data into a byte[]s obtained from an underlying BufferPool. Which
fixes all of the above. There is still an issue where the total
memory allocation may grow when switching up bitrate, but we can
easily fix that from this point, if we choose to restrict the buffer
based on allocation size rather than time.

Issue: #278

2015-02-13 19:32:01 +00:00

..

doc/images

Bring internal/external branches closer.

2014-11-19 15:58:26 +00:00

src/main

Finally - Remove Sample, fix GC churn + inefficient memory usage.

2015-02-13 19:32:01 +00:00

build.gradle

Include gradle plugin 1.0.0

2014-12-22 10:34:46 +08:00