From owner-freebsd-stable@FreeBSD.ORG Sat Jan 12 01:21:29 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 2421316A420; Sat, 12 Jan 2008 01:21:29 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id E4C0F13C448; Sat, 12 Jan 2008 01:21:28 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.8/8.13.8) with ESMTP id m0C1LQix000571; Fri, 11 Jan 2008 20:21:26 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id m0C1LQWS064767 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Jan 2008 20:21:26 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200801120121.m0C1LQWS064767@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 11 Jan 2008 20:21:29 -0500 To: Kris Kennaway , Krassimir Slavchev From: Mike Tancsa In-Reply-To: <4787A41C.70100@FreeBSD.org> References: <476A5EE1.9000003@bulinfo.net> <476FF662.6050604@FreeBSD.org> <477BB7C0.3060603@bulinfo.net> <4787A41C.70100@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: FreeBSD Subject: Re: Performance! [SOLVED] 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: Sat, 12 Jan 2008 01:21:29 -0000 At 12:15 PM 1/11/2008, Kris Kennaway wrote: >Just to summarize some discussion we had off-list, this problem is >now resolved. It turned out to have two causes: > >1) sysbench on linux was defaulting to using a unix domain socket to >communicate with pgsql, but FreeBSD was using TCP to 127.0.0.1. TCP >has much more overhead so performance was lower. Using >--pgsql-host="" in sysbench is the fix for this. > >2) pgsql was not compiled with thread support enabled, which caused >lots of bad interactions with the threaded sysbench client. This >probably would have caused data corruption too (silent in this case >because nothing was checking the query responses). The fix was to >recompile the pgsql client and server with the THREADSAFE option enabled. Thats great news! Just for the record, for build options are there any other options that need to be set other than # diff -u Makefile.default Makefile --- Makefile.default 2008-01-11 20:13:06.000000000 -0500 +++ Makefile 2008-01-11 20:16:02.000000000 -0500 @@ -87,7 +87,7 @@ OPTIONS+= HEIMDAL_KRB5 "Builds with Heimdal kerberos support" off OPTIONS+= OPTIMIZED_CFLAGS "Builds with compiler optimizations (-O3)" off OPTIONS+= LIBC_R "Link w/ libc_r, used by plpython (server)" off -OPTIONS+= THREADSAFE "make libpq thread safe" off +OPTIONS+= THREADSAFE "make libpq thread safe" on # to run regression tests: OPTIONS+= TESTS "Allows the use of a \"check\" target (server)" off OPTIONS+= DEBUG "Builds with debugging symbols" off ? In terms of the kernel was this with ULE or SCHED_4BSD ? ---Mike