Bug 1303866 - Review Request: lz4-java - LZ4 compression for Java
Summary: Review Request: lz4-java - LZ4 compression for Java
Keywords:
Status: CLOSED DUPLICATE of bug 1270317
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: 23
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-02 09:31 UTC by Tomas Repik
Modified: 2016-02-08 23:19 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-02-08 09:39:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tomas Repik 2016-02-02 09:31:40 UTC
Spec URL: https://trepik.fedorapeople.org/lz4-java.spec
SRPM URL: https://trepik.fedorapeople.org/lz4-java-1.3.0-1.fc23.src.rpm

Description: Provides access to two compression methods that both generate a valid LZ4 stream. First one is fast scan (LZ4) which has low memory footprint (~ 16 KB). It is very fast (fast scan with skipping heuristics in case the input looks in-compressible). The method also has a reasonable compression ratio (depending on the redundancy of the input). Second one is high compression (LZ4 HC) with medium memory footprint (~ 256 KB).It is rather slow (~ 10 times slower than LZ4). The method has a good compression ratio (depending on the size and the redundancy of the input). The streams produced by those two compression algorithms use the same compression format, are very fast to decompress and can be decompressed by the same decompressor instance.

Fedora Account System Username: trepik

Comment 1 gil cattaneo 2016-02-02 18:45:52 UTC
Hi.
This bug is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1270317

Comment 2 gil cattaneo 2016-02-03 16:36:45 UTC
Please, close this bug if you want import/use my work

Comment 3 Tomas Repik 2016-02-08 09:39:58 UTC

*** This bug has been marked as a duplicate of bug 1270317 ***


Note You need to log in before you can comment on or make changes to this bug.