You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Karl von Randow (JIRA)" <ji...@apache.org> on 2015/10/16 05:04:05 UTC

[jira] [Created] (LUCENE-6841) LZ4 compression using too much CPU time

Karl von Randow created LUCENE-6841:
---------------------------------------

             Summary: LZ4 compression using too much CPU time
                 Key: LUCENE-6841
                 URL: https://issues.apache.org/jira/browse/LUCENE-6841
             Project: Lucene - Core
          Issue Type: Bug
          Components: core/codecs
    Affects Versions: 5.3.1
         Environment: Linux, Java 8
            Reporter: Karl von Randow


I am using Lucene for search indexing, including storing a large number of small fields, and some larger plain text fields, and searching using both exact matches and analyzed queries.

LZ4 (specifically the decompress method) is using nearly exactly 50% of the application's CPU time.

It seems to me that LZ4 is inappropriate for my use case. I note that I can choose BEST_SPEED or BEST_COMPRESSION.

Would it be palatable to add a NO_COMPRESSION option, or some way to pick and choose which fields get compressed? Perhaps a minimum length of a field could be specified before it's compressed? I'm not sure if that's possible.

If this approach, or similar is palatable, I would be happy to contribute a patch (or to consume and test a patch).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org