lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Elschot (JIRA)" <>
Subject [jira] Commented: (LUCENE-1410) PFOR implementation
Date Fri, 03 Oct 2008 18:31:44 GMT


Paul Elschot commented on LUCENE-1410:

Q: We should look at the asm that's produced?
A: Maybe. But would that be java bytecodes or x86 or powerpc? I'd prefer to wait with that.
There are some nice machine instrns to this on the various architectures, but that would require
to use native code.

Q: But can I also get the "bytes consumed" when I ask decompress() to run?
A; Yes, but only after decompression or after compression.
The number of exceptions is not explicitly coded in the header, so the size to encode the
exceptions is not known beforehand. That could be changed, but than the header will get bigger.
(For compression, it's possible to do a run without buffer first.)

Block size 128 should be fine, one could also try 64 and 32.

Thanks for posting the links here, they are the ones I used to code this up. (Does that count
as homework? :) )
I did not put the links in the code because of possible link rot. The article titles and authors
are in the javadocs.
Currently the easy way to find the links is via google scholar.

> PFOR implementation
> -------------------
>                 Key: LUCENE-1410
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: Other
>            Reporter: Paul Elschot
>            Priority: Minor
>         Attachments: LUCENE-1410b.patch,
>   Original Estimate: 21840h
>  Remaining Estimate: 21840h
> Implementation of Patched Frame of Reference.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message