From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 19:42:06 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B35D316A418 for ; Tue, 5 Feb 2008 19:42:06 +0000 (UTC) (envelope-from tom@samplonius.org) Received: from ly.sdf.com (ly.sdf.com [216.113.193.83]) by mx1.freebsd.org (Postfix) with ESMTP id 66F3B13C4D1 for ; Tue, 5 Feb 2008 19:42:06 +0000 (UTC) (envelope-from tom@samplonius.org) Received: from localhost (localhost [127.0.0.1]) by ly.sdf.com (Postfix) with ESMTP id 678EC37C002; Tue, 5 Feb 2008 11:38:07 -0800 (PST) X-Virus-Scanned: amavisd-new at X-Spam-Score: -4.044 X-Spam-Level: X-Spam-Status: No, score=-4.044 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, AWL=0.355, BAYES_00=-2.599] Received: from ly.sdf.com ([127.0.0.1]) by localhost (ly.sdf.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4acmma4xsC1A; Tue, 5 Feb 2008 11:37:58 -0800 (PST) Received: from ly.sdf.com (ly.sdf.com [216.113.193.83]) by ly.sdf.com (Postfix) with ESMTP id 0721937C001; Tue, 5 Feb 2008 11:37:58 -0800 (PST) Date: Tue, 5 Feb 2008 11:37:57 -0800 (PST) From: Tom Samplonius To: Primeroz lists Message-ID: <28875927.5811202240277979.JavaMail.root@ly.sdf.com> In-Reply-To: <55b8c6fe0802040450r7ca3e739s931be2d38f499fc2@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [64.251.80.98] Cc: freebsd-stable@freebsd.org Subject: Re: Crashing repeatedly: 6.2-RELEASE-p5 and MySQL 5.0.41 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2008 19:42:06 -0000 ----- "Primeroz lists" wrote: > Hi all, > > we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or > 2). > > FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram. > > MySQL Version is 5.0.41 with following configuration settings: > > set-variable = key_buffer=768M > set-variable = table_cache=800 > set-variable = sort_buffer=24M > set-variable = myisam_sort_buffer_size=256M > set-variable = record_buffer=16M > set-variable = max_allowed_packet=10M > set-variable = thread_stack=128K > set-variable = join_buffer=512M > set-variable = max_heap_table_size=256M > set-variable = max_connections=300 > set-variable = tmp_table_size=384M > set-variable = query_cache_size=402653184 > set-variable = query_cache_limit=134217728 > set-variable = read_rnd_buffer_size=10M > set-variable = ft_min_word_len=1 > pid-file = /var/db/mysqld.pid > tmpdir = /var/tmp > ft_stopword_file = '' > set-variable = thread_cache_size=80 > set-variable = myisam_stats_method=nulls_equal Also, myslq is not really well tuned. The query cache is a kludge. It is helpful, if you have stupid application that issues the same query over and over again, even though the database has not changed. If you don't have this problem, it just adds overhead. And quite a lot, if it is big. Generally, the query cache should be 20 to 100M at most, if not disabled. If you have a smart web application (anything using memcached), the query cache should just be turned off. It will actually be faster. You should give us much storage as possible to the database engine, for it cache actual data, not query results. It is weird that you are apparently are heavily using Innodb, but you have just set various myiasam values? Here is something useful: http://www.joyeur.com/2007/09/25/quick-wins-with-mysql Tom