Not really. With off-line use, you can amortize the cost of sorting across all items. This allows very tight encodings in some cases. In on-line (real-time actually) use you have the problem that you can't amortize anything because you have a worst case constraint.
Essentially, this is the difference between hadoop and OLTP relational databases. On Mon, Aug 31, 2009 at 10:34 AM, Sean Owen <sro...@gmail.com> wrote: > This is definitely for on-line use. Though I imagine strategies for > efficient storage pertain well to both the off- and on-line case. > -- Ted Dunning, CTO DeepDyve
