From owner-freebsd-questions@FreeBSD.ORG Wed Jul 19 18:51:47 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6EAE16A4DA for ; Wed, 19 Jul 2006 18:51:47 +0000 (UTC) (envelope-from thaddeus@dm1.net) Received: from mail.dm1.net (mail.dm1.net [162.39.20.85]) by mx1.FreeBSD.org (Postfix) with SMTP id 0E74B43D45 for ; Wed, 19 Jul 2006 18:51:46 +0000 (GMT) (envelope-from thaddeus@dm1.net) Received: (qmail 26678 invoked from network); 19 Jul 2006 18:52:58 -0000 Received: from unknown (HELO ?192.168.1.49?) (thaddeus@192.168.1.49) by mail.dm1.net with SMTP; 19 Jul 2006 18:52:58 -0000 Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <96460F2A-A74E-4A5F-ACB5-A40ABD133298@mac.com> References: <407487AA-A1C4-4581-A7EA-2FBC68E284C6@dm1.net> <653A9EA4-19F7-41E8-BDD4-E0906C997D6E@dm1.net> <96460F2A-A74E-4A5F-ACB5-A40ABD133298@mac.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <0542DE13-1181-4050-9545-2595BB4C0A42@dm1.net> Content-Transfer-Encoding: 7bit From: Thaddeus Quintin Date: Wed, 19 Jul 2006 14:51:44 -0400 To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.752.2) Subject: Re: Memory usage for MySQL X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2006 18:51:47 -0000 On Jul 19, 2006, at 2:37 PM, Charles Swiger wrote: > On Jul 19, 2006, at 2:31 PM, Thaddeus Quintin wrote: >> I already took care of that, it was in my first email- >>>> I tweaked /boot/loader.conf to allow larger data size for >>>> processes already (rebooted after changes)- >>>> kern.maxdsiz="1395864371" # 1.3GB >>>> kern.dfldsiz="1395864371" # 1.3GB >>>> kern.maxssiz="134217728" # 128MB >> >> From what I read, that should do it, but I still get those start >> up errors before MySQL decides to run. Maybe it has something to >> do with how quickly MySQL is asking for memory? > > Or maybe it's trying to ask for a big shared memory segment...? Your guess is as good as mine. Are there tools or anything else I can use to try and figure this out? Thaddeus