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 C697418C7E for ; Mon, 8 Feb 2016 15:45:57 +0000 (UTC) Received: (qmail 7648 invoked by uid 500); 8 Feb 2016 15:45:53 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 7574 invoked by uid 500); 8 Feb 2016 15:45:53 -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 7562 invoked by uid 99); 8 Feb 2016 15:45:53 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Feb 2016 15:45:53 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id AB3EE1A0227 for ; Mon, 8 Feb 2016 15:45:52 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.129 X-Spam-Level: ** X-Spam-Status: No, score=2.129 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id JBtvTH3vtRmJ for ; Mon, 8 Feb 2016 15:45:51 +0000 (UTC) Received: from mail-yw0-f180.google.com (mail-yw0-f180.google.com [209.85.161.180]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 2B5722050D for ; Mon, 8 Feb 2016 15:45:51 +0000 (UTC) Received: by mail-yw0-f180.google.com with SMTP id h129so104805851ywb.1 for ; Mon, 08 Feb 2016 07:45:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=oPsXuHNT05DqTf1do5Ul3o9DFNcwaXnRchH6Twmku54=; b=kYsQf/L/PiOnlqwZGA496PzjOgxvXH0eRu5d7gUzLOXe/82EHDLymifdCSIJmQW2OV PDZTFpAyUMY6iY05g2IKz3e/tT1T+7wRd04epGwIRAWXvV4KJF8Q1UP9UUiST2p1zo6T kD6yIYJ9Q8nDgvNeHwUI14Pat5Z/ChoWs1Hu68t5Wlzv4D7VVybgDXYVuKGgadWidVe2 30EnE3N7ycBCKYndRi71dPDXjBy9Cq5PAOgRDQfdBybvOhDq8PXsh4DPJKMZMf+WSwtb wVGwdrqFLP58nnPNd0HTBiJVR+ymbBbY/GaikgNwqZ1Q5vLtYTcrkIq08rDrcowpqTum 1zIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=oPsXuHNT05DqTf1do5Ul3o9DFNcwaXnRchH6Twmku54=; b=U0jaSyvg2oeE3dzNLVqgBW8YEqeYYG5WCpIXGobTP7itp3RN4J5D5OPfaODqXQsJvv 6vJFJhuD8+pKWGR2xsWGcRgTWnPqhQisKTV8LjcSiQ+nZFpX5f0jSRBDW/Dqc2jdWtZo SMQmdg6F7bkGEqzuvlBOS8+GMrn8c3afnX+19yge5U31xUD0uZw8BGCG5qgZLp+vM7zB CyYX/cEBEqmp5uHABDNg1QOJrj97fwJOQJ10FgGc9NUorr8ZE1AKvJWcLEhqW/Puz2H3 arfuuPciofXCcIVR1wVfMx2JLERVskwum6ixvoQB8QwkEy1gxXVaCTlF61bJR9o5PqVW 166w== X-Gm-Message-State: AG10YOQDSYmh2gXF3gotaV0PPYOb8qpmtWdrunGXovvdk/gzW1kPuH3j4lEv8n9/TR/pBnIfR7mMwIVIufsakg== MIME-Version: 1.0 X-Received: by 10.13.244.4 with SMTP id d4mr16449271ywf.343.1454946350428; Mon, 08 Feb 2016 07:45:50 -0800 (PST) Received: by 10.13.210.198 with HTTP; Mon, 8 Feb 2016 07:45:50 -0800 (PST) In-Reply-To: References: <56B8614B.9090000@sematext.com> Date: Mon, 8 Feb 2016 10:45:50 -0500 Message-ID: Subject: Re: solr performance issue From: Susheel Kumar To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary=94eb2c034e8c627a22052b441838 --94eb2c034e8c627a22052b441838 Content-Type: text/plain; charset=UTF-8 1 million document shouldn't have any issues at all. Something else is wrong with your hw/system configuration. Thanks, Susheel On Mon, Feb 8, 2016 at 6:45 AM, sara hajili wrote: > On Mon, Feb 8, 2016 at 3:04 AM, sara hajili wrote: > > > sorry i made a mistake i have a bout 1000 K doc. > > i mean about 1000000 doc. > > > > On Mon, Feb 8, 2016 at 1:35 AM, Emir Arnautovic < > > emir.arnautovic@sematext.com> wrote: > > > >> Hi Sara, > >> Not sure if I am reading this right, but I read it as you have 1000 doc > >> index and issues? Can you tell us bit more about your setup: number of > >> servers, hw, index size, number of shards, queries that you run, do you > >> index at the same time... > >> > >> It seems to me that you are running Solr on server with limited RAM and > >> probably small heap. Swapping for sure will slow things down and GC is > most > >> likely reason for high CPU. > >> > >> You can use http://sematext.com/spm to collect Solr and host metrics > and > >> see where the issue is. > >> > >> Thanks, > >> Emir > >> > >> -- > >> Monitoring * Alerting * Anomaly Detection * Centralized Log Management > >> Solr & Elasticsearch Support * http://sematext.com/ > >> > >> > >> > >> On 08.02.2016 10:27, sara hajili wrote: > >> > >>> hi all. > >>> i have a problem with my solr performance and usage hardware like a > >>> ram,cup... > >>> i have a lot of document and so indexed file about 1000 doc in solr > that > >>> every doc has about 8 field in average. > >>> and each field has about 60 char. > >>> i set my field as a storedfield = "false" except of 1 field. // i read > >>> that this help performance. > >>> i used copy field and dynamic field if it was necessary . // i read > that > >>> this help performance. > >>> and now my question is that when i run a lot of query on solr i faced > >>> with > >>> a problem solr use more cpu and ram and after that filled ,it use a lot > >>> swapped storage and then use hard,but doesn't create a system file! > >>> solr > >>> fill hard until i forced to restart server to release hard disk. > >>> and now my question is why solr treat in this way? and how i can avoid > >>> solr > >>> to use huge cpu space? > >>> any config need?! > >>> > >>> > >> > > > --94eb2c034e8c627a22052b441838--