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 >> > >