[Xapian-discuss] Ranking and term proximity

[goran kent]

On Tue, Sep 6, 2011 at 12:31 PM, William Crawford
<william at sciencephoto.co.uk> wrote:
> I've got an index that's about 700M, on a server with 24G RAM, and I'd much
> rather have the faster search that comes from /not/ trying too hard to
> compress the data. I understand there are use-cases where everything can't be
> cached, but perhaps there's a need for either two backends (mono- and megalith
> would be good names?) or a flag to pass to the WritableDatabase when creating?

Exactly, storage is cheap.  Who cares how much space it consumes if
the trade-off is blistering performance.

The whole point of inverted indexes is search performance, is it not?