2
66%
master: 66%

Ran 03 Apr 2017 12:09AM UTC

Files 37

Run time 1s

Badge

Embed ▾

Committed 03 Apr 2017 12:07AM UTC coverage: 65.77% (+0.7%) from 65.07%

Job # 201.2

Build Type

Pull #39

travis-ci

Committed by

web-flow

Commit Message

Make direct buffer allocation optional

This is a minor refactoring of all codecs that directly allocate Java `ByteBuffers`: instead of making a direct call to `ByteBuffer#allocate()`, the codec invokes a protected method `makeBuffer(size)`. This allows a user to subclass the codec and override the method to customize the buffer allocation.

In particular, this enables users to use heap-buffers and/or buffer pooling. The latter is essential for reducing memory churn.

In a JVM benchmark (not included) on some real-world data, this refactoring did not decrease performance. (Notice that dropping `final` from some classes does not stop the JVM from inlining, such as in [monomorphic callsites](https://shipilev.net/blog/2015/black-magic-method-dispatch/).)

Pull Request Pull Request #39: Make direct buffer allocation optional

Run Details

5893 of 8960 relevant lines covered (65.77%)

0.66 hits per line

lemire / JavaFastPFOR / 201 / 2
66%
master: 66%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 201.2

lemire / JavaFastPFOR / 201 / 2 66% master: 66%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 201.2

lemire / JavaFastPFOR / 201 / 2
66%
master: 66%

README BADGES
x