Yes, I created different workers and with same or different queries. sorry it has been a while since I used it, and the link to its source code (no jars) should be here: http://code.google.com/p/httpstone/source/checkout
sunnyfr wrote: > > just a question about your httpstone's configuration ....? > I would like to know how did you simulate several word search ... ?? > Did you create a lot of different workers with lof of different word > search ? > > Thanks, > > > zqzuk wrote: >> >> Hi, >> >> try to firstly have a look at http://wiki.apache.org/solr/SolrCaching the >> section on firstsearcher and warming. Search engines rely on caching, so >> first searches will be slow. I think to be fair testing it is necessary >> to warm up the search engine by sending most frequently used and/or most >> costly queries, then start your stress testing. >> >> I used this tool http://code.google.com/p/httpstone/ to do stress >> testing. It allows you to create multiple threads sending queries to a >> server simultaneously, and records time taken to process each query in >> each thread. >> >> Hope it helps. >> >> >> >> sunnyfr wrote: >>> >>> Hi, >>> >>> I'm trying as well to stress test solr. I would love some advice to >>> manage it properly. >>> I'm using solr 1.3 and tomcat55. >>> Thanks a lot, >>> >>> >>> zqzuk wrote: >>>> >>>> Hi, I am doing a stress testing of my solr application to see how many >>>> concurrent requests it can handle and how long it takes. But I m not >>>> sure if I have done it in proper way... responses seem to be very slow >>>> >>>> My configuration: >>>> 1 Solr instance, using the default settings distributed in the example >>>> code, while I made two changes: >>>> <useColdSearcher>true</useColdSearcher> >>>> <maxWarmingSearchers>10</maxWarmingSearchers> >>>> As I thought the more searchers the more concurrent requests can be >>>> dealt with? >>>> >>>> There are 1.1 million documents indexed, and the platform is winxp sp2, >>>> duo core 1.8 GB machine with ram 2GB >>>> >>>> I used httpstone, a simple server load testing tool to create 100 >>>> workers (so 100 threads) each issuing one same query to the server. To >>>> deal with a single request of this query it took solr 2 seconds (with >>>> facet counts), and 7 documents are returned. I was assuming that only >>>> first request would take longer time and following requests should be >>>> almost instantaneous as the query is the same. But strange that the >>>> first response took as long as 20 seconds. >>>> >>>> It looked like that the 100 workers sent same request to solr and then >>>> all of a sudden solr server went silent. Only after 20 seconds some of >>>> these workers started to receive responses, but still very slow. >>>> >>>> clearly there I must have made something wrong with configuring solr >>>> server... Could you give me some pointers on how to improve the >>>> performance please? >>>> >>>> Many thanks! >>>> >>> >>> >> >> > > -- View this message in context: http://www.nabble.com/how-to-improve-concurrent-request-performance-and-stress-testing-tp15299687p20229678.html Sent from the Solr - User mailing list archive at Nabble.com.
