Bug 1303866

Summary:	Review Request: lz4-java - LZ4 compression for Java
Product:	[Fedora] Fedora	Reporter:	Tomas Repik <trepik>
Component:	Package Review	Assignee:	Nobody's working on this, feel free to take it <nobody>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	23	CC:	msuchy, package-review, puntogil
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-08 09:39:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 ***