From owner-freebsd-current@FreeBSD.ORG Mon Jun 14 19:03:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07E0A16A4D0; Mon, 14 Jun 2004 19:03:02 +0000 (GMT) Received: from mail.ngdc.net (mail.ngdc.net [195.190.153.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69E7D43D53; Mon, 14 Jun 2004 19:03:01 +0000 (GMT) (envelope-from laursen@netgroup.dk) Received: from animal (port390.ds1-noe.adsl.cybercity.dk [217.157.177.19]) (AUTH: LOGIN laursen@solidcore.dk) by bunsen.solidcore.dk with esmtp; Mon, 14 Jun 2004 21:02:38 +0200 Message-ID: <02c601c45242$240df470$6401a8c0@animal> From: "Lasse Laursen" To: "Daniel Eischen" References: Date: Mon, 14 Jun 2004 21:01:58 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: freebsd-current@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: Possible Threading problem with -CURRENT / MySQL? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2004 19:03:02 -0000 Hi, Please find answers below: Regards -- Lasse Laursen · VP, Hosting Technology · NetGroup Processing Aps St. Kongensgade 40H · DK-1264 Copenhagen K, Denmark Phone: +45 3370 1526 · Fax: +45 3313 0066 - Don't be fooled by cheap finnish imitations - BSD is the One True Code ----- Original Message ----- From: "Daniel Eischen" To: "Lasse Laursen" Cc: ; Sent: Monday, June 14, 2004 8:58 PM Subject: Re: Possible Threading problem with -CURRENT / MySQL? > > WE use the SCHED_ULE, and: > > > > # Memory options > > options MAXDSIZ="(1536*1024*1024)" > > options MAXSSIZ="(1024*1024*1024)" > > options DFLDSIZ="(1536*1024*1024)" > > Try using SCHED_4BSD, then try removing all memory options. Wouldn't this limit us to 512 MB of memory per process running on the server? we tried with each scheduler with same results. I will try to recompile without the memory options and use the old scheduler. Any hints why this might work?