Skip to content
This repository has been archived by the owner on May 4, 2023. It is now read-only.

Benchmark on performance of Indexing and Searching #253

Open
uditabose opened this issue Jul 16, 2017 · 1 comment
Open

Benchmark on performance of Indexing and Searching #253

uditabose opened this issue Jul 16, 2017 · 1 comment

Comments

@uditabose
Copy link

Hi,
For my project, I have to about 700GB of text and HTML which produces Lucene index about 19GB. The indexing process took about 30 hours last time. Do you have any data on benchmarking? Things I need to understand are -

  1. Does CouchDB fetch performance deteriorate if the indexing added to it?
  2. What impact couchdb-lucene had on indexing performance? Is performance similar to a native java client ?
@rnewson
Copy link
Owner

rnewson commented Jul 31, 2017

I don't have benchmarking data for Lucene itself beyond the general observation that it's pretty fast.

couchdb-lucene will add some cost as it needs to evaluate javascript functions to produce the output.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants