Re: fast static alphabetic (order preserving) compression algorithms/implementations
- From: "cr88192" <cr88192@xxxxxxxxxxx>
- Date: Fri, 13 Jul 2007 16:19:28 +1000
<bryan@xxxxxxxxxx> wrote in message
news:1184074144.652912.275520@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jul 9, 3:29 pm, John Reiser <jrei...@xxxxxxxxxxxx> wrote:
I am looking to identify a fast static alphabetic (order preserving)
compression algorithm for database indices (B+Trees) ...
"Lossless" did not appear in your list of requirements.
In other words, hashing is OK. Therefore, select an ordered subset
of the original bits, such as:
the even-numbered bits, or
the prime-numbered bits, or
the Fibonacci-numbered bits, etc.
Across all possible distributions of inputs, this is as good
as possible anyway.
--
Can it be order preserving if it is lossy?
this depends...
with this scheme, it is possible that important bits would be missed,
leading to a broken order if it is possible to add new keys later (this
would seem to be a non-trivial problem).
I would probably opt with a lossless approach, such as huffman, or stick
with raw bytes.
.
- References:
- Prev by Date: Re: Employing a set of data files guaranteed to be available at the time of decompression
- Next by Date: Re: Employing a set of data files guaranteed to be available at the time of decompression
- Previous by thread: Re: fast static alphabetic (order preserving) compression algorithms/implementations
- Next by thread: Re: fast static alphabetic (order preserving) compression algorithms/implementations
- Index(es):
Relevant Pages
|
|