Return-Path: Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: (qmail 38028 invoked from network); 8 Oct 2009 22:25:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Oct 2009 22:25:09 -0000 Received: (qmail 92156 invoked by uid 500); 8 Oct 2009 22:25:07 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 92087 invoked by uid 500); 8 Oct 2009 22:25:07 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 92077 invoked by uid 99); 8 Oct 2009 22:25:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Oct 2009 22:25:07 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [208.97.132.83] (HELO homiemail-a22.g.dreamhost.com) (208.97.132.83) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Oct 2009 22:24:56 +0000 Received: from infr-laptop7.olx.com.ar (unknown [201.216.209.201]) by homiemail-a22.g.dreamhost.com (Postfix) with ESMTPA id 117B01A805F for ; Thu, 8 Oct 2009 15:24:34 -0700 (PDT) From: Grant Ingersoll Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Subject: [slightly off topic] Jetty and NIO Date: Thu, 8 Oct 2009 19:24:33 -0300 Message-Id: To: solr-user@lucene.apache.org Mime-Version: 1.0 (Apple Message framework v1076) X-Mailer: Apple Mail (2.1076) X-Virus-Checked: Checked by ClamAV on apache.org In the Solr example jetty.xml, there is the following setup and comments: 50000 1500 So, if I'm on Centos 2.6 (64 bit), what connector should I be using? Based on the comments, I'm not sure the top one is the right thing either, but it also sounds like it is my only other choice. The other thing I'm noticing is if I profile my app and I am retrieving something like 50 rows at a time, 30-60% of the time is spent in org.mortbay.jetty.bio.SocketConnector$Connection.fill(). I realize the answer may just be to get less results, but I was wondering if there are other tuning parameters that can make this more efficient b/c the 50 rows thing is a biz. reqt and I may not be able to get that changed. Thanks, Grant