Re: scalability w/ number of fields

2005-04-06 Thread Yonik Seeley
Thanks Doug, your previous comment led us to consider compound field types of the form compound:"name=value". Open ended range queries also need some manipulation for this scheme to work. > Yes, this is an ugly hack, but it can make a huge performance > differrence. The problem is that Lucene st

Re: scalability w/ number of fields

2005-04-06 Thread Doug Cutting
Yonik Seeley wrote: They are all indexed (and they all need to be under the current design). As I mentioned before, Lucene will not perform well with a large number of indexed fields. If these are not tokenized fields, then a simple way to reduce the number of indexed fields is to move the field

Re: scalability w/ number of fields

2005-04-05 Thread Yonik Seeley
Optimize performance update (with tons of indexed fields): We had a timing bug... ignore the hour I first reported. Here are the current numbers: indexed_fields=6791 index_size=3.9GB optimize_time=21min indexed_fields=3216 index_size=2.0GB optimize_time=9min indexed_fields=2080 index_size=1

Re: scalability w/ number of fields

2005-04-05 Thread Bill Au
The compound index structure is meant for indexes with a large number of fields. I was watching the files in the index directory of my compound index while it was being optimized. The IndexWriter that I used was set to use compound file. It looks to me that Lucene first combined all existing segme

Re: scalability w/ number of fields

2005-04-04 Thread Yonik Seeley
They are all indexed (and they all need to be under the current design). -Yonik On Apr 4, 2005 6:16 PM, Doug Cutting <[EMAIL PROTECTED]> wrote: > Yonik Seeley wrote: > > I know Lucene is very scalable in many ways, but how about number of > > fieldnames? > > > > We have an index using around 600

Re: scalability w/ number of fields

2005-04-04 Thread Doug Cutting
Yonik Seeley wrote: I know Lucene is very scalable in many ways, but how about number of fieldnames? We have an index using around 6000 unique fieldnames, How many of these fields are indexed? At this point I would recommend against having more than a handful of indexed fields. If the fields are

scalability w/ number of fields

2005-04-04 Thread Yonik Seeley
Oops, sorry. First went to dev by accident. -- Forwarded message -- I know Lucene is very scalable in many ways, but how about number of fieldnames? We have an index using around 6000 unique fieldnames, 450,000 documents, and a total index size of 4GB. It's very sparse... docum