One criteria for testing is to assume that a certain number of users that
are searching against a particular field (for example product_name) in
parallel are all using unique terms.
Therefore, I would like to use my search index to gather all the unique
terms that are seen during indexing from a particular field ... and use
this as a dictionary in a JMeter test to assign all unique search words to
different threads/users and figure out what the performance would be like
in this scenario ... where users don't have the benefit of searching for
similar terms whose results have already been cached.
I think that the Lucene toolkit already provides a SpellChecker module that
does something similar but I'm wondering:
- Does Elasticsearch already has this capability baked-in somewhere and it
is as easy as making the right call? If so, please point me to it. - If I used Lucene's SpellChecker module to point to a ES built index then
can I expect to be able to simply read it w/o any locking issues while ES
is running? - Rather than locating, building a path & feeding it in as a Directory
into SpellChecker ... would there happen be a better integration point from
which to leverage the ES built indices in code?
Thanks!
- Pulkit
On Fri, Mar 2, 2012 at 7:48 AM, pulkitsinghal pulkitsinghal@gmail.comwrote:
I am aiming for the ability to reuse a template on specific datasets
and user workflows to find out the performance for each unique
ecosystem (data + types of queries + # of parallel queries for each
type + users + use-cases etc.) and what it means to come up with a
formula so that one is ready to scale ES.To that end, I found everyone's suggestions have been really useful, I
count:
- JMeter
- SoapUI
- XLT
I will get started on a template for JMeter based test-harness, and
will post back here when I have a prototype. If someone does the same
using the other tools, I would be thankful & welcome any sharing on
your part tooCheers!
On Mar 1, 2:11 pm, Jan Fiedler fiedler....@gmail.com wrote:
I have been using XLT (
Xceptance - XLT for Load and Performance Testing) for all sorts of
load testing. Its especially nice if your home (and preferred ES API) is
Java as you write your load scripts in Java as JUnit test.