Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 457B710AF1 for ; Tue, 30 Dec 2014 02:43:54 +0000 (UTC) Received: (qmail 44680 invoked by uid 500); 30 Dec 2014 02:43:47 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 44612 invoked by uid 500); 30 Dec 2014 02:43:47 -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 44600 invoked by uid 99); 30 Dec 2014 02:43:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Dec 2014 02:43:45 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of apache@elyograg.org designates 166.70.79.219 as permitted sender) Received: from [166.70.79.219] (HELO frodo.elyograg.org) (166.70.79.219) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Dec 2014 02:43:41 +0000 Received: from localhost (localhost [127.0.0.1]) by frodo.elyograg.org (Postfix) with ESMTP id 738784E8D for ; Mon, 29 Dec 2014 19:42:38 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elyograg.org; h= content-transfer-encoding:content-type:content-type:in-reply-to :references:subject:subject:mime-version:user-agent:from:from :date:date:message-id:received:received; s=mail; t=1419907357; bh=1cPQaQRwIT20iOkk1KblsY7D5pdwWQJ4FIUhngAt/+A=; b=QFOWLiVlvyeh xxo4/smTvs7u0EnkxUcs0S1WOwpIeFjKHuX6WZ1Quh+Y3Xmzi0Ab3DDhCgdAN0Ex llJ8UVOS1O3fX3JGDmaT4iceltAqSqHlBUmLO89m64Hg5eoO4KzCbGR9PFhUyxKm yC+oz+oW8zsNykac/icbOLWF8Bhd0ac= X-Virus-Scanned: Debian amavisd-new at frodo.elyograg.org Received: from frodo.elyograg.org ([127.0.0.1]) by localhost (frodo.elyograg.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id IB7DhhZkCiZb for ; Mon, 29 Dec 2014 19:42:37 -0700 (MST) Received: from [192.168.1.102] (102.int.elyograg.org [192.168.1.102]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: elyograg@elyograg.org) by frodo.elyograg.org (Postfix) with ESMTPSA id C36454AED for ; Mon, 29 Dec 2014 19:42:37 -0700 (MST) Message-ID: <54A2111D.5040803@elyograg.org> Date: Mon, 29 Dec 2014 19:42:37 -0700 From: Shawn Heisey User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: solr-user@lucene.apache.org Subject: Re: How large is your solr index? References: <54A1724A.4060607@intix.eu> <2E6A89A648463A4EBF093A9062C1668305A857EDF673@SBMAILBOX1.sb.statsbiblioteket.dk> In-Reply-To: <2E6A89A648463A4EBF093A9062C1668305A857EDF673@SBMAILBOX1.sb.statsbiblioteket.dk> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 12/29/2014 2:30 PM, Toke Eskildsen wrote: > At Lucene/Solr Revolution 2014, Grant Ingersoll also asked for user stories and pointed to https://wiki.apache.org/solr/SolrUseCases - sadly it has not caught on. The only entry is for our (State and University Library, Denmark) setup with 21TB / 7 billion documents on a single machine. To follow my own advice, I can elaborate that we have 1-3 concurrent users and a design goal of median response times below 2 seconds for faceted search. I guess that is at the larger end at the spectrum for pure size, but at the very low end for usage. Off-Topic tangent: I believe it would be useful to organize a session at Lucene Revolution, possibly more interactive than a straight presentation, where users with very large indexes are encouraged to attend. The point of this session would be to exchange war stories, configuration requirements, hardware requirements, and observations. Bringing people with similar goals together to discuss their solutions should be beneficial. The discussions could pinpoint areas where Solr and SolrCloud are weak on scalability, and hopefully lead to issues in Jira and fixes for those problems. Better documentation for extreme scaling is also a possible outcome. Another idea, not sure if it would be good as an alternate idea or supplemental, is a less formal gathering, perhaps over a meal or three. My index is hardly large enough to mention, but I would be interested in attending such a gathering to learn more about the topic. Thanks, Shawn