Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 61651 invoked from network); 21 Mar 2007 20:59:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Mar 2007 20:59:01 -0000 Received: (qmail 8356 invoked by uid 500); 21 Mar 2007 20:59:02 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 8331 invoked by uid 500); 21 Mar 2007 20:59:02 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 8320 invoked by uid 99); 21 Mar 2007 20:59:02 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Mar 2007 13:59:02 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of casspc@gmail.com designates 209.85.132.242 as permitted sender) Received: from [209.85.132.242] (HELO an-out-0708.google.com) (209.85.132.242) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Mar 2007 13:58:51 -0700 Received: by an-out-0708.google.com with SMTP id c3so427886ana for ; Wed, 21 Mar 2007 13:58:30 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=o5DbMz0NChpjqhF0JOa5x+tKhTlcNLg4dQSsubQMHKu27gbwN99GwmwMQVu1/Umr6iJHdAnEyuK5dzKitqSdc1goKllhN6xokVO4Qg4BS6Iae4AFahfckY9YK1s6Q5jSj2yrn2Oa5Z/523qXvtCMfpVnHWHPpsLbyTgc02UcuHg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=Y8vuoHrYN9zmm1hvCJ/Q8ITS01/60lgahIML+svBHwD9eRME9CvFbXt+l2fPpMVx93TjS50SnelpNv2elnkaztW4kWzAXmOq/VsgFfDRUme3DBVWg7eY5MsKgNyRemEm9uX0cqozgrdA8b6YrCfNkHyt7mSQ5PB2pDrwiY7D2QY= Received: by 10.100.57.14 with SMTP id f14mr930219ana.1174510709771; Wed, 21 Mar 2007 13:58:29 -0700 (PDT) Received: by 10.100.45.20 with HTTP; Wed, 21 Mar 2007 13:58:29 -0700 (PDT) Message-ID: <8e69b6620703211358n267fa33avb87b33f65ef0e868@mail.gmail.com> Date: Wed, 21 Mar 2007 13:58:29 -0700 From: "Cass Costello" To: java-user@lucene.apache.org Subject: Re: Thank you... In-Reply-To: <8e69b6620703211259y3efb6d54nbde2e335195faba8@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_148092_26702210.1174510709716" References: <8e69b6620703201258o38d18f05j8f5010c48ca195a8@mail.gmail.com> <0ef901c76b2b$b0f6d280$0301a8c0@tmesa.com> <8e69b6620703201349k35aecfe1ka1c27b6962081c9@mail.gmail.com> <8e69b6620703211259y3efb6d54nbde2e335195faba8@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_148092_26702210.1174510709716 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline You all rock. I'm clearing the semi-official legal hurdle with my CTO and our head counsel to full (or something close to full) disclosure of some of the architectural details, so stay tuned for as much as I'm allowed to share (and btw, for any of you that live/work/vacation in the SF Bay area, I'd be happy to discuss things over a beer :) In the meantime, yes, much of the faceting you see on the Browse and Search pages is direct Solr faceting. We made *very* liberal use of faceting-specific fields in our event and ontology documents. Similarly, we rely on the standard query handler for almost all the Solr calls. Our business logic is modelled in a CoR pattern, and we did write one command to encapsulate SolrCore/Request/Response use for our highest throughput needs - the win there was direct building into our predominant xml object model (we use XOM) via a QueryResponseXOMBuilder.build( solrRequest, solrResponse ) call. I definitely need clearance before sharing hard perf numbers (anyone working for TicketMaster on these lists? - funny, I used to use "eBay" in lines like that - see below) but I will share the fact that our response times and q/s numbers were very good out-of-the-box. We've an Ehcache-based distributed caching framework that we threw in front of the Solr servers, and our final total throughput for the Solr queries utilized to support Browse runs into the 100's of requests per sec, per Solr server. Our Search (true free-text searches) numbers are lower, but not by that much. This might be the coolest (for me, anyway) result of the entire endeavor... StubHub was recently acquired by eBay. I've been working closely with a couple of their architects over the past few weeks, and we've done a bit of theoretical, comparative analysis between our search/browse platform and theirs (which is completely home grown), and things stack up favorably for the Solr/Lucene approach, esp. when considering the *vast* difference in hardware allocation per-request. Again, if I'm allowed, more details to follow. >>...I've taken the liberty of adding stubhub to the "Powered By" Solr page... Awesome. I can't say it enough... thank you all. On 3/21/07, Yonik Seeley wrote: > > On 3/20/07, Cass Costello wrote: > > Heh - it used to be in my sig ... my bad. > > > > Thanks, all. :) > > > > http://www.stubhub.com > > I tried it out... looks great! > Is the faceting stuff done with Solr too? > If so is it the Solr built-in faceting, or a custom query handler? If > the latter, can you think of ways to improve the built in faceting > that would have made things easier? > > -Yonik > -- A complex system that works is invariably found to have evolved from a simple system that works. - John Gaule -- A complex system that works is invariably found to have evolved from a simple system that works. - John Gaule ------=_Part_148092_26702210.1174510709716--