This sounds like a neat patch -- what changes are you exploring to Collector?

These days when I need to test indexing or searching performance I
usually use the Python scripts from here:

    https://hg.codespot.com/a/apache-extras.org/luceneutil

Unfortunately they are rather involved to set up (which we need to fix)...

If you open a Jira issue and attach a patch I'd be happy to performance test it.

Mike McCandless

http://blog.mikemccandless.com

On Wed, Sep 7, 2011 at 3:35 AM, Anne Veling <a...@beyondtrees.com> wrote:
> I've been following the Lucene/Solr community for a long time and finally
> have found (or: taken) the time to start implementing some of my ideas how
> to improve on it; this will be my first proposed patch.
> I'm working on some changes to the Collector API to significantly improve
> the performance of some use cases, but my change may have a negative effect
> on other use cases (though I doubt it), including memory resources. Of
> course such an effect would only be measurable for larger index sizes.
> My question is: how can I best test this? Is there a common dataset/index
> that is used to verify that patches do not degrade search performance? I can
> do some testing on my own wikipedia index of course, but I guess that
> aligning with the performance tools you guys are using, will be better
> Thank you, keep up the good work,
> Anne
>
> --
> Anne Veling
> BeyondTrees.com
> +31 6 50 969 170
> @anneveling
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to