Re: Improving performance to return 2000+ documents

2013-06-30 Thread Jagdish Nomula
t; > > > > allText is a copyField. > > > > > > > > > > > > This is the result I get: > > > > > > ubuntu@ip-10-149-6-68:~$ ab -c 10 -n 500 " > > > > > > > > > > > > > > > > > > > > > http://x.amazonaws.com:8983/solr/prodinfo/select?q=allText:huggies%20diapers%20size%201&rows=2000&wt=json > > > > > > " > > > > > > > > > > > > Benchmarking x.amazonaws.com (be patient) > > > > > > Completed 100 requests > > > > > > Completed 200 requests > > > > > > Completed 300 requests > > > > > > Completed 400 requests > > > > > > Completed 500 requests > > > > > > Finished 500 requests > > > > > > > > > > > > > > > > > > Server Software: > > > > > > Server Hostname:x.amazonaws.com > > > > > > Server Port:8983 > > > > > > > > > > > > Document Path: > > > > > > > > > > > > > > > > > > > > > /solr/prodinfo/select?q=allText:huggies%20diapers%20size%201&rows=2000&wt=json > > > > > > Document Length:1538537 bytes > > > > > > > > > > > > Concurrency Level: 10 > > > > > > Time taken for tests: 35.999 seconds > > > > > > Complete requests: 500 > > > > > > Failed requests:21 > > > > > >(Connect: 0, Receive: 0, Length: 21, Exceptions: 0) > > > > > > Write errors: 0 > > > > > > Non-2xx responses: 2 > > > > > > Total transferred: 766221660 bytes > > > > > > HTML transferred: 766191806 bytes > > > > > > Requests per second:13.89 [#/sec] (mean) > > > > > > Time per request: 719.981 [ms] (mean) > > > > > > Time per request: 71.998 [ms] (mean, across all concurrent > > > > > requests) > > > > > > Transfer rate: 20785.65 [Kbytes/sec] received > > > > > > > > > > > > Connection Times (ms) > > > > > > min mean[+/-sd] median max > > > > > > Connect:00 0.6 0 8 > > > > > > Processing: 9 717 2339.6199 12611 > > > > > > Waiting:9 635 2233.6164 12580 > > > > > > Total: 9 718 2339.6199 12611 > > > > > > > > > > > > Percentage of the requests served within a certain time (ms) > > > > > > 50%199 > > > > > > 66%236 > > > > > > 75%263 > > > > > > 80%281 > > > > > > 90%548 > > > > > > 95%838 > > > > > > 98% 12475 > > > > > > 99% 12545 > > > > > > 100% 12611 (longest request) > > > > > > > > > > > > -- > > > > > > Thanks, > > > > > > -Utkarsh > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Thanks, > > > > > -Utkarsh > > > > > > > > > > > > > > > > > > > > -- > > Thanks, > > -Utkarsh > > > -- ***Jagdish Nomula* Sr. Manager Search Simply Hired, Inc. 370 San Aleso Ave., Ste 200 Sunnyvale, CA 94085 office - 408.400.4700 cell - 408.431.2916 email - jagd...@simplyhired.com www.simplyhired.com

Looking for Search Engineers

2013-06-18 Thread Jagdish Nomula
revenue and relevance for search queries(aka multi-objective maximization problem) d) Helping people find jobs If you are interested in helping us out, please send your resume across. Thanks, *Jagdish Nomula* Sr. Manager Search Simply Hired, Inc. 370 San Aleso Ave., Ste 200 Sunnyvale, CA 94085

Re: Search for misspelled words in corpus

2013-06-09 Thread Jagdish Nomula
okens > > Otis > -- > Solr & ElasticSearch Support > http://sematext.com/ > > > > > > On Sun, Jun 9, 2013 at 2:30 AM, Jagdish Nomula > wrote: > > Another theoretical answer for this question is ngrams approach. You can > > index the word

Re: Search for misspelled words in corpus

2013-06-08 Thread Jagdish Nomula
> > search > > > term. > > > We tried fuzzy search, but it doesn't work as per our expectations. It > > > returns any close match, not specifically misspelled words. For > example, > > if > > > I'm searching for a word like "fi

Re: Solr 4.2.1 Branch

2013-04-05 Thread Jagdish Nomula
; > > > -- Jack Krupansky > > -Original Message- From: Jagdish Nomula Sent: Friday, April 05, > 2013 8:36 PM To: solr-user@lucene.apache.org Subject: Solr 4.2.1 Branch > Hello, > > I was trying to get hold of solr 4.2.1 branch on github. I see > https://github.com/apache/

Solr 4.2.1 Branch

2013-04-05 Thread Jagdish Nomula
Hello, I was trying to get hold of solr 4.2.1 branch on github. I see https://github.com/apache/lucene-solr/tree/lucene_solr_4_2. I don't see any branch for 4.2.1. Am i missing anything ?. Thanks in advance for your help. -- ***Jagdish Nomula* Sr. Manager Search Simply Hired, Inc. 37

Re: Convert Complex Lucene Query to SolrQuery

2013-01-09 Thread Jagdish Nomula
1 PM, Jack Krupansky wrote: > How complex? Does it use any of the more advanced Query Types or detailed > options that are not supported in the Solr query syntax? > > What specific problems did you have. > > -- Jack Krupansky > > -Original Message- From: Jagdish Nomula >

Convert Complex Lucene Query to SolrQuery

2013-01-08 Thread Jagdish Nomula
Hello Solr Users, I am trying to convert a complex lucene query to solrquery to use it in a embeddedsolrserver instance. I have tried the regular toString method without success. Is there any suggested method to do this ?. Greatly appreciate the response. Thanks, -- Jagadish Nomula - Seni

Search Engineers at SimplyHired.com

2013-01-04 Thread Jagdish Nomula
Hello Solr-Users, I thought you, or someone you know, might be interested in a very important role here at Simply Hired. The Staff Search Engineer will own the responsibility of writing the search engine of SimplyHired. You will work on cutting edge machine learning, search and big data tools