A normal Lucene index should be able to handle it.
As long as no frequent insert/update, which can sometimes cause hiccups for
large indexes, one index is enough.
If your customer numbers keep growing, you will need to have one index for
each customer, which isn't that difficult really, especiall
: Multiple indexes vs single index
Hi,
> You get one answer if each document is 1K, another if it's
> 1G. If you have 2 users or 10,000 users. If you require
> 100 queries/sec response time or 1 query can take 10
> seconds. If you require an update to the index every
> second o
Hi,
> You get one answer if each document is 1K, another if it's
> 1G. If you have 2 users or 10,000 users. If you require
> 100 queries/sec response time or 1 query can take 10
> seconds. If you require an update to the index every
> second or month...
Each doc has up to 10 A4 pages text.
There
Define efficiency. Define document. Define user. Define
This kind of question is unanswerable except in gross
generalities unless you take the time to provide details.
You get one answer if each document is 1K, another if it's
1G. If you have 2 users or 10,000 users. If you require
100 querie
Hi,
We have have an application which manages the data of multiple customers.
A customer can only search its own data, never the data of other customers.
So what is more efficent in respect of performance and resources:
One big single index filtered by an index field (customer-Id) or multiple
sm
