, February 6, 2012 1:17 AM
Subject: effect of continuous deletes on index's read performance
I have a use case where documents are continuously added @ 20 docs/sec
( each doc add is also doing a commit ) and docs continuously getting
deleted at the same rate. So the searchable index size remains
-usersolr-user@lucene.apache.org
Sent: Monday, February 6, 2012 1:17 AM
Subject: effect of continuous deletes on index's read performance
I have a use case where documents are continuously added @ 20 docs/sec
( each doc add is also doing a commit ) and docs continuously getting
deleted at the same rate
of continuous deletes on index's read performance
I have a use case where documents are continuously added @ 20 docs/sec
( each doc add is also doing a commit ) and docs continuously getting
deleted at the same rate. So the searchable index size remains the
same : ~ 400K docs ( docs for last 6 hours
On Mon, Feb 6, 2012 at 8:20 AM, prasenjit mukherjee
prasen@gmail.com wrote:
Pardon my ignorance, Why can't the IndexWriter and IndexSearcher share
the same underlying in-memory datastructure so that IndexSearcher need
not be reopened with every commit.
Because the semantics of an
I have a use case where documents are continuously added @ 20 docs/sec
( each doc add is also doing a commit ) and docs continuously getting
deleted at the same rate. So the searchable index size remains the
same : ~ 400K docs ( docs for last 6 hours ~ 20*3600*6).
Will it have pauses when
, February 6, 2012 1:17 AM
Subject: effect of continuous deletes on index's read performance
I have a use case where documents are continuously added @ 20 docs/sec
( each doc add is also doing a commit ) and docs continuously getting
deleted at the same rate. So the searchable index size remains
: Monday, February 6, 2012 1:17 AM
Subject: effect of continuous deletes on index's read performance
I have a use case where documents are continuously added @ 20 docs/sec
( each doc add is also doing a commit ) and docs continuously getting
deleted at the same rate. So the searchable index size