Date: Thu, 16 Apr 1998 14:50:44 +0900 (JST) From: Michael Hancock <michaelh@cet.co.jp> To: Atipa <freebsd@atipa.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Status of native threads on CURRENT / Support for mySQL Message-ID: <Pine.SV4.3.95.980416144257.9006B-100000@parkplace.cet.co.jp> In-Reply-To: <Pine.BSF.3.96.980415202100.28522A-100000@altrox.atipa.com>
next in thread | previous in thread | raw e-mail | index | archive | help
If you're looking for stability in a production environment stay away from current for a little while as there is a lot of new activity including vm/vfs/cam/softupdates/elf/posix/microtime/alpha/sparc that's going to take a little while to settle even with careful planning and testing. I think thread work is suspended until some dependent underlying vm projects are completed. Regards, Mike On Wed, 15 Apr 1998, Atipa wrote: > Hi everyone, > > Can anyone help me out on the status of threads in -CURRENT? I am a bit > confused as to when to use the following: > > 1) pthreads > 2) libc_r (reentrant-safe/thread-safe libc?) > 3) MIT threads and other 3rd part threads > > I need to make a fast, reliable database server (mySQL). I am currently > using 2.2.6-STABLE w/ MIT threads, but MIT threads do not support unix > sockets and are not native to the OS. But then again, I am a bit worried > about the current stability of threading on -CURRENT. I have seen several > complaints about missing functionality and possible bugs. > > Is there a noticable performance difference between mySQL on 2.2.6 and on > -CURRENT? If so,... > > Does anyone have any experience / recommnedations for mySQL on -CURRENT? > Would these recommendations be altered by using an SMP kernel? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SV4.3.95.980416144257.9006B-100000>