Re: Measuring SOLR performance

2013-08-01 Thread Dmitry Kan
Hi Roman,

When I try to run with -q
/home/dmitry/projects/lab/solrjmeter/queries/demo/demo.queries

here what is reported:
Traceback (most recent call last):
  File solrjmeter.py, line 1390, in module
main(sys.argv)
  File solrjmeter.py, line 1309, in main
tests = find_tests(options)
  File solrjmeter.py, line 461, in find_tests
with changed_dir(pattern):
  File /usr/lib/python2.7/contextlib.py, line 17, in __enter__
return self.gen.next()
  File solrjmeter.py, line 229, in changed_dir
os.chdir(new)
OSError: [Errno 20] Not a directory:
'/home/dmitry/projects/lab/solrjmeter/queries/demo/demo.queries'

Best,

Dmitry



On Wed, Jul 31, 2013 at 7:21 PM, Roman Chyla roman.ch...@gmail.com wrote:

 Hi Dmitry,
 probably mistake in the readme, try calling it with -q
 /home/dmitry/projects/lab/solrjmeter/queries/demo/demo.queries

 as for the base_url, i was testing it on solr4.0, where it tries contactin
 /solr/admin/system - is it different for 4.3? I guess I should make it
 configurable (it already is, the endpoint is set at the check_options())

 thanks

 roman


 On Wed, Jul 31, 2013 at 10:01 AM, Dmitry Kan solrexp...@gmail.com wrote:

  Ok, got the error fixed by modifying the base solr ulr in solrjmeter.py
  (added core name after /solr part).
  Next error is:
 
  WARNING: no test name(s) supplied nor found in:
  ['/home/dmitry/projects/lab/solrjmeter/demo/queries/demo.queries']
 
  It is a 'slow start with new tool' symptom I guess.. :)
 
 
  On Wed, Jul 31, 2013 at 4:39 PM, Dmitry Kan solrexp...@gmail.com
 wrote:
 
  Hi Roman,
 
  What  version and config of SOLR does the tool expect?
 
  Tried to run, but got:
 
  **ERROR**
File solrjmeter.py, line 1390, in module
  main(sys.argv)
File solrjmeter.py, line 1296, in main
  check_prerequisities(options)
File solrjmeter.py, line 351, in check_prerequisities
  error('Cannot contact: %s' % options.query_endpoint)
File solrjmeter.py, line 66, in error
  traceback.print_stack()
  Cannot contact: http://localhost:8983/solr
 
 
  complains about URL, clicking which leads properly to the admin page...
  solr 4.3.1, 2 cores shard
 
  Dmitry
 
 
  On Wed, Jul 31, 2013 at 3:59 AM, Roman Chyla roman.ch...@gmail.com
 wrote:
 
  Hello,
 
  I have been wanting some tools for measuring performance of SOLR,
 similar
  to Mike McCandles' lucene benchmark.
 
  so yet another monitor was born, is described here:
 
 http://29min.wordpress.com/2013/07/31/measuring-solr-query-performance/
 
  I tested it on the problem of garbage collectors (see the blogs for
  details) and so far I can't conclude whether highly customized G1 is
  better
  than highly customized CMS, but I think interesting details can be seen
  there.
 
  Hope this helps someone, and of course, feel free to improve the tool
 and
  share!
 
  roman
 
 
 
 



Re: Measuring SOLR performance

2013-07-31 Thread Dmitry Kan
Hi Roman,

What  version and config of SOLR does the tool expect?

Tried to run, but got:

**ERROR**
  File solrjmeter.py, line 1390, in module
main(sys.argv)
  File solrjmeter.py, line 1296, in main
check_prerequisities(options)
  File solrjmeter.py, line 351, in check_prerequisities
error('Cannot contact: %s' % options.query_endpoint)
  File solrjmeter.py, line 66, in error
traceback.print_stack()
Cannot contact: http://localhost:8983/solr


complains about URL, clicking which leads properly to the admin page...
solr 4.3.1, 2 cores shard

Dmitry


On Wed, Jul 31, 2013 at 3:59 AM, Roman Chyla roman.ch...@gmail.com wrote:

 Hello,

 I have been wanting some tools for measuring performance of SOLR, similar
 to Mike McCandles' lucene benchmark.

 so yet another monitor was born, is described here:
 http://29min.wordpress.com/2013/07/31/measuring-solr-query-performance/

 I tested it on the problem of garbage collectors (see the blogs for
 details) and so far I can't conclude whether highly customized G1 is better
 than highly customized CMS, but I think interesting details can be seen
 there.

 Hope this helps someone, and of course, feel free to improve the tool and
 share!

 roman



Re: Measuring SOLR performance

2013-07-31 Thread Dmitry Kan
Ok, got the error fixed by modifying the base solr ulr in solrjmeter.py
(added core name after /solr part).
Next error is:

WARNING: no test name(s) supplied nor found in:
['/home/dmitry/projects/lab/solrjmeter/demo/queries/demo.queries']

It is a 'slow start with new tool' symptom I guess.. :)


On Wed, Jul 31, 2013 at 4:39 PM, Dmitry Kan solrexp...@gmail.com wrote:

 Hi Roman,

 What  version and config of SOLR does the tool expect?

 Tried to run, but got:

 **ERROR**
   File solrjmeter.py, line 1390, in module
 main(sys.argv)
   File solrjmeter.py, line 1296, in main
 check_prerequisities(options)
   File solrjmeter.py, line 351, in check_prerequisities
 error('Cannot contact: %s' % options.query_endpoint)
   File solrjmeter.py, line 66, in error
 traceback.print_stack()
 Cannot contact: http://localhost:8983/solr


 complains about URL, clicking which leads properly to the admin page...
 solr 4.3.1, 2 cores shard

 Dmitry


 On Wed, Jul 31, 2013 at 3:59 AM, Roman Chyla roman.ch...@gmail.comwrote:

 Hello,

 I have been wanting some tools for measuring performance of SOLR, similar
 to Mike McCandles' lucene benchmark.

 so yet another monitor was born, is described here:
 http://29min.wordpress.com/2013/07/31/measuring-solr-query-performance/

 I tested it on the problem of garbage collectors (see the blogs for
 details) and so far I can't conclude whether highly customized G1 is
 better
 than highly customized CMS, but I think interesting details can be seen
 there.

 Hope this helps someone, and of course, feel free to improve the tool and
 share!

 roman





Re: Measuring SOLR performance

2013-07-31 Thread Roman Chyla
Hi Dmitry,
probably mistake in the readme, try calling it with -q
/home/dmitry/projects/lab/solrjmeter/queries/demo/demo.queries

as for the base_url, i was testing it on solr4.0, where it tries contactin
/solr/admin/system - is it different for 4.3? I guess I should make it
configurable (it already is, the endpoint is set at the check_options())

thanks

roman


On Wed, Jul 31, 2013 at 10:01 AM, Dmitry Kan solrexp...@gmail.com wrote:

 Ok, got the error fixed by modifying the base solr ulr in solrjmeter.py
 (added core name after /solr part).
 Next error is:

 WARNING: no test name(s) supplied nor found in:
 ['/home/dmitry/projects/lab/solrjmeter/demo/queries/demo.queries']

 It is a 'slow start with new tool' symptom I guess.. :)


 On Wed, Jul 31, 2013 at 4:39 PM, Dmitry Kan solrexp...@gmail.com wrote:

 Hi Roman,

 What  version and config of SOLR does the tool expect?

 Tried to run, but got:

 **ERROR**
   File solrjmeter.py, line 1390, in module
 main(sys.argv)
   File solrjmeter.py, line 1296, in main
 check_prerequisities(options)
   File solrjmeter.py, line 351, in check_prerequisities
 error('Cannot contact: %s' % options.query_endpoint)
   File solrjmeter.py, line 66, in error
 traceback.print_stack()
 Cannot contact: http://localhost:8983/solr


 complains about URL, clicking which leads properly to the admin page...
 solr 4.3.1, 2 cores shard

 Dmitry


 On Wed, Jul 31, 2013 at 3:59 AM, Roman Chyla roman.ch...@gmail.comwrote:

 Hello,

 I have been wanting some tools for measuring performance of SOLR, similar
 to Mike McCandles' lucene benchmark.

 so yet another monitor was born, is described here:
 http://29min.wordpress.com/2013/07/31/measuring-solr-query-performance/

 I tested it on the problem of garbage collectors (see the blogs for
 details) and so far I can't conclude whether highly customized G1 is
 better
 than highly customized CMS, but I think interesting details can be seen
 there.

 Hope this helps someone, and of course, feel free to improve the tool and
 share!

 roman






Re: Measuring SOLR performance

2013-07-31 Thread Shawn Heisey

On 7/31/2013 10:21 AM, Roman Chyla wrote:

Hi Dmitry,
probably mistake in the readme, try calling it with -q
/home/dmitry/projects/lab/solrjmeter/queries/demo/demo.queries

as for the base_url, i was testing it on solr4.0, where it tries
contactin /solr/admin/system - is it different for 4.3? I guess I should
make it configurable (it already is, the endpoint is set at the
check_options())


/solr URLs that don't include a core name (like /solr/admin/system) will 
only work if you have a defaultCoreName attribute in your solr.xml file 
and its value refers to an existing core.  Behind the scenes, Solr just 
directs those queries to the default core.


If you use the new solr.xml format (required in trunk), then there is no 
defaultCoreName, so these URLs currently don't work at all.  I think 
this behavior is correct, but it's early days for this feature.  The 
default core name might get re-introduced.


Exceptions to the above rule include the CoreAdmin API, the Collections 
API, and the new admin info handler introduced in Solr 4.4 by SOLR-4943.


In 4.5, SOLR-3633 will use the new info handler allow the UI to work 
when there are no cores present.


Thanks,
Shawn


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



Re: Measuring SOLR performance

2013-07-31 Thread Roman Chyla
On Wed, Jul 31, 2013 at 1:21 PM, Shawn Heisey s...@elyograg.org wrote:

 On 7/31/2013 10:21 AM, Roman Chyla wrote:

 Hi Dmitry,
 probably mistake in the readme, try calling it with -q
 /home/dmitry/projects/lab/**solrjmeter/queries/demo/demo.**queries

 as for the base_url, i was testing it on solr4.0, where it tries
 contactin /solr/admin/system - is it different for 4.3? I guess I should
 make it configurable (it already is, the endpoint is set at the
 check_options())


 /solr URLs that don't include a core name (like /solr/admin/system) will
 only work if you have a defaultCoreName attribute in your solr.xml file and
 its value refers to an existing core.  Behind the scenes, Solr just directs
 those queries to the default core.


thanks, so i should add a way to specify a core, or rather i will make the
whole endpoint user configurable



 If you use the new solr.xml format (required in trunk), then there is no
 defaultCoreName, so these URLs currently don't work at all.  I think this
 behavior is correct, but it's early days for this feature.  The default
 core name might get re-introduced.


and which urls will work? /solr/admin/collection or /solr/collection/admin?
can we assume the info handlers will be available under the collection
url as well?




 Exceptions to the above rule include the CoreAdmin API, the Collections
 API, and the new admin info handler introduced in Solr 4.4 by SOLR-4943.

 In 4.5, SOLR-3633 will use the new info handler allow the UI to work when
 there are no cores present.


hmm, ok, i guess i'm fine now, i'll worry about that later

roman


 Thanks,
 Shawn


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




Re: Measuring SOLR performance

2013-07-31 Thread Shawn Heisey

On 7/31/2013 3:32 PM, Roman Chyla wrote:

thanks, so i should add a way to specify a core, or rather i will make
the whole endpoint user configurable


Good plan.


and which urls will work? /solr/admin/collection or
/solr/collection/admin? can we assume the info handlers will be
available under the collection url as well?


The URL for the CoreAdmin API handler is:

/solr/admin/cores

Similarly, the URL for the Collections API is the following, but without 
URL parameters, this one won't do anything useful at this

time:

/solr/admin/collections

For some reason I thought SOLR-4943 had been committed to Solr 4.4, but 
it's not there.  In 4.5, you'll be able to access the following URL 
without a core name in the URL or the defaultCoreName setting in solr.xml:


/solr/admin/info/system

There are also some other info handler URLs, see SOLR-4943 comments.

Thanks,
Shawn


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



Measuring SOLR performance

2013-07-30 Thread Roman Chyla
Hello,

I have been wanting some tools for measuring performance of SOLR, similar
to Mike McCandles' lucene benchmark.

so yet another monitor was born, is described here:
http://29min.wordpress.com/2013/07/31/measuring-solr-query-performance/

I tested it on the problem of garbage collectors (see the blogs for
details) and so far I can't conclude whether highly customized G1 is better
than highly customized CMS, but I think interesting details can be seen
there.

Hope this helps someone, and of course, feel free to improve the tool and
share!

roman