Github user bodewig commented on the issue:
https://github.com/apache/commons-compress/pull/13
I just realized I had benchmarked compression rather than decompression,
I've now updated
https://github.com/bodewig/commons-compress-benchmarks/wiki/PR13
Fortunately the result is
Github user bodewig commented on the issue:
https://github.com/apache/commons-compress/pull/13
@thomasmey I've made some minor changes and pushed it to the branch PR13
My benchmarks at
https://github.com/bodewig/commons-compress-benchmarks/wiki/PR13 sees the
changed code
Github user bodewig commented on the issue:
https://github.com/apache/commons-compress/pull/13
For starters, https://github.com/bodewig/commons-compress-benchmarks -
right now I'm not sure where it'll end up.
---
If your project is set up for it, you can reply to this email and have
Github user bodewig commented on the issue:
https://github.com/apache/commons-compress/pull/13
I'm planning to set up a JMH based benchmark soonish and would like to get
some statistical information before merging this.
---
If your project is set up for it, you can reply to this
Github user bodewig commented on the issue:
https://github.com/apache/commons-compress/pull/13
Sorry, I didn't realize you had updated the PR, will have a look later.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user coveralls commented on the issue:
https://github.com/apache/commons-compress/pull/13
[![Coverage
Status](https://coveralls.io/builds/9753579/badge)](https://coveralls.io/builds/9753579)
Coverage increased (+0.1%) to 83.502% when pulling
Github user coveralls commented on the issue:
https://github.com/apache/commons-compress/pull/13
[![Coverage
Status](https://coveralls.io/builds/9753579/badge)](https://coveralls.io/builds/9753579)
Coverage increased (+0.1%) to 83.502% when pulling
Github user bodewig commented on the issue:
https://github.com/apache/commons-compress/pull/13
Some rough comparisons for larger files would be a good indicator.
The existing code is pretty ugly because this seemed to be necessary for
acceptable performance back then. "Back
Github user thomasmey commented on the issue:
https://github.com/apache/commons-compress/pull/13
Don't know. How to test? I think it very much depends on target
architecture and JVM implementation. I could try to establish a baseline with a
test case to check for regression. what do
Github user ebourg commented on the issue:
https://github.com/apache/commons-compress/pull/13
Is the performance equivalent with a BitInputStream?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user coveralls commented on the issue:
https://github.com/apache/commons-compress/pull/13
[![Coverage
Status](https://coveralls.io/builds/9678824/badge)](https://coveralls.io/builds/9678824)
Coverage decreased (-0.009%) to 83.361% when pulling
11 matches
Mail list logo