From owner-freebsd-stable Wed Dec 12 19:41:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 715DB37B416 for ; Wed, 12 Dec 2001 19:41:13 -0800 (PST) Received: from mail2.uniserve.com ([204.244.156.10]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 16EMk5-00078W-00; Wed, 12 Dec 2001 19:41:05 -0800 Date: Wed, 12 Dec 2001 19:41:05 -0800 (PST) From: Tom X-Sender: tom@athena.uniserve.ca To: David Xu Cc: Andrew Tulloch , freebsd-stable@FreeBSD.ORG Subject: Re: SMP and MySQL/threads In-Reply-To: <3C17FA33.3070906@viasoft.com.cn> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 13 Dec 2001, David Xu wrote: > If you need performance, keep it with Linux until FreeBSD 5.0 is ready. > current pthread implement in FreeBSD 4 is user level thread, and all > disk access will > be serialized and whole threads can only run in one processor. Disk access will be serialized? pthreads is all userland, which is true, but all userland programs can issue non-blocking IO requests. pthreads does (must) use nonblocking IO. No one seems to have mentioned any MySQL thread issues. For instance, most MySQL table types serialize all INSERT and UPDATEs. Only one thread can be writing at a time. A new table type fixes this problem, but currently lacks online backup! Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message