[ 
https://issues.apache.org/jira/browse/LUCENE-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654812#action_12654812
 ] 

[EMAIL PROTECTED] edited comment on LUCENE-1483 at 12/9/08 6:55 AM:
--------------------------------------------------------------

I'll be sure to include that info with the next set of results. 

I don't think those results represent getting lucky though: its 4 rounds and 2 
runs with the same results (17% both runs). Nothing scientific, just did it 
real quick to get a base feel of the slowdown before the patch is finished up.

Here is the alg I used:

{noformat}

merge.factor=mrg:50
compound=false

sort.rng=20000:10000:20000:10000

analyzer=org.apache.lucene.analysis.standard.StandardAnalyzer
directory=FSDirectory
#directory=RamDirectory

doc.stored=true
doc.tokenized=true
doc.term.vector=false
doc.add.log.step=100000

docs.dir=reuters-out

doc.maker=org.apache.lucene.benchmark.byTask.feeds.SortableSimpleDocMaker

query.maker=org.apache.lucene.benchmark.byTask.feeds.SimpleQueryMaker

# task at this depth or less would print when they start
task.max.depth.log=2

log.queries=true
# 
-------------------------------------------------------------------------------------

{ "Rounds"
        { "Run"
      ResetSystemErase

      { "Populate"
        -CreateIndex
        { "MAddDocs" AddDoc(100) > : 500000
        -CloseIndex
      }
    
      { "TestSortSpeed"
        OpenReader  
        { "LoadFieldCacheAndSearch" SearchWithSort(sort_field:int) > : 1 
        { "SearchWithSort" SearchWithSort(sort_field) > : 5000
        CloseReader 
      
      }
    
      NewRound
     } : 4

} 

RepSumByName

{noformat}

      was (Author: [EMAIL PROTECTED]):
    I'll be sure to include that info with the next set of results. 

I don't think those results represent getting lucky though: its 4 rounds and 2 
runs with the same results (17% both runs). Nothing scientific, just did it 
real quick to get a base feel of the slowdown before the patch is finished up.

Here is the alg I used:

{noformat}

merge.factor=mrg:50
compound=false

sort.rng=20000:10000:20000:10000

analyzer=org.apache.lucene.analysis.standard.StandardAnalyzer
directory=FSDirectory
#directory=RamDirectory

doc.stored=true
doc.tokenized=true
doc.term.vector=false
doc.add.log.step=100000

docs.dir=reuters-out

doc.maker=org.apache.lucene.benchmark.byTask.feeds.SortableSimpleDocMaker

query.maker=org.apache.lucene.benchmark.byTask.feeds.SimpleQueryMaker

# task at this depth or less would print when they start
task.max.depth.log=2

log.queries=true
# 
-------------------------------------------------------------------------------------

{ "Rounds"
        { "Run"
      ResetSystemErase

      { "Populate"
        -CreateIndex
        { "MAddDocs" AddDoc(100) > : 500000
        -Optimize
        -CloseIndex
      }
    
      { "TestSortSpeed"
        OpenReader  
        { "LoadFieldCacheAndSearch" SearchWithSort(sort_field:int) > : 1 
        { "SearchWithSort" SearchWithSort(sort_field) > : 5000
        CloseReader 
      
      }
    
      NewRound
     } : 4

} 

RepSumByName

{noformat}
  
> Change IndexSearcher to use MultiSearcher semantics for sorted searches
> -----------------------------------------------------------------------
>
>                 Key: LUCENE-1483
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1483
>             Project: Lucene - Java
>          Issue Type: Improvement
>    Affects Versions: 2.9
>            Reporter: Mark Miller
>            Priority: Minor
>         Attachments: LUCENE-1483.patch
>
>
> Here is a quick test patch. FieldCache for sorting is done at the individual 
> IndexReader level and reloading the fieldcache on reopen can be much faster 
> as only changed segments need to be reloaded.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to