This has been discussed many times on the list, you'd find a wealth of information if you searched the mail archive.
The problem usually is that you've stored your dates with fine resolution. Sorting is dependent on the number of terms, and if you store millisecond resolution you'll obviously have waaaaaay more terms than if you store second resolution. Day resolution is even better. Also your first sort takes much longer than subsequent sorts since various caches aren't filled until needed. So be sure you're measuring response times after a few sorted queries have happened. Best Erick On Wed, Apr 9, 2008 at 2:27 AM, savageboy <[EMAIL PROTECTED]> wrote: > > Hello everyone, > I have made a search project by use of Lucene2.0 > But when I use date sorting, the server is running very slow for the > result > getting(about 3 sec but I dont sort the results the time of it is about > 0.019 sec, there are 110000 results to be hit). > > document.add(new Field(docFieldName, > StringUtils.defaultIfEmpty(contentStr, > ""), storeFlag , tokenizeFlag)); > > storeFlag is true > tokenizeFlag is false > > so it means the Field dateTime should be stored and be not tokenized! > > If you have some idea about this issue I met, plz let me know! > Thanks a lot and best Regards! > > > -- > View this message in context: > http://www.nabble.com/Fetches-the-hits-very-slow-%28when-the-date-sorting%29-%21-tp16580375p16580375.html > Sent from the Lucene - Java Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
