Hi, Just thought this possibility: I think dynamic field is solr concept, on lcene level all fields are the same, but in initial startup, lucene should load all field information into memory (not field data, but schema).
If we have too many fields (like *_my_fields, * => a1, a2, ...), does this take too much memory and slow down performance (even if very few fields are really used)? Best regards, Lisheng -----Original Message----- From: Upayavira [mailto:u...@odoko.co.uk] Sent: Monday, January 07, 2013 2:57 PM To: solr-user@lucene.apache.org Subject: Re: theory of sets Dynamic fields resulted in poor response times? How many fields did each document have? I can't see how a dynamic field should have any difference from any other field in terms of response time. Or are you querying across a large number of dynamic fields concurrently? I can imagine that slowing things down. Upayavira On Mon, Jan 7, 2013, at 05:18 PM, Uwe Reh wrote: > Hi Robi, > > thank you for the contribution. It's exiting to read, that your index > isn't contaminated by the number of fields. I can't exclude other > mistakes, but my first experience with extensive use of dynamic fields > have been very poor response times. > > Even though I found an other solution, I should give the straight > forward solution a second chance. > > Uwe > > Am 07.01.2013 17:40, schrieb Petersen, Robert: > > Hi Uwe, > > > > We have hundreds of dynamic fields but since most of our docs only use some > > of them it doesn't seem to be a performance drag. They can be viewed as a > > sparse matrix of fields in your indexed docs. Then if you make the > > sortinfo_for_groupx an int then that could be used in a function query to > > perform your sorting. See http://wiki.apache.org/solr/FunctionQuery >
