Date: Wed, 27 Aug 2003 20:05:24 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: Gordon Tetlow <gordont@gnf.org> Cc: threads@freebsd.org Subject: Re: Call for thread testers Message-ID: <Pine.GSO.4.10.10308272003290.9892-100000@pcnet5.pcnet.com> In-Reply-To: <20030827235853.GH695@roark.gnf.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 27 Aug 2003, Gordon Tetlow wrote: > On Wed, Aug 27, 2003 at 10:05:28AM -0600, Scott Long wrote: > > All, > > > > This is kind of an unconventional call for help. As we approach the > > release of 5.2, we'd really like to show off the performance and > > stability of our new threading packages. So, I'm looking for people > > to volunteer to go out and put some of the thread-capable enterprise > > and desktop packages to the test. Packages that I would most like > > to see are: > > > > Apache 2 > > BIND 9 > > OpenOffice > > Mozilla > > KDE desktop + Konq > > Java 1.3/1.4 + Tomcat/etc > > MySQL > > Others? > > I've found that privoxy is a good program to test threads. It does > alot of network io too. ports/www/privoxy. Just point your web browser > to use it. > > > The questions that I would like to have answered are: > > > > Does it take advantage of pthreads > Yes. > > Does it work with libkse and libthr > Sort of. > > Does it operate correctly > libthr: tends to segfault (sig11). Occasional DNS resolution issues. > libkse: tends to segfault (sig11), I've gotten my box to crash > once too (BAD!). ^C still doesn't kill the process. > Occasional DNS resolution issues. Here's the output from the > console: > > Aug 27 10:22:41 Privoxy(134991872) Request: images.slashdot.org/greendot.gif > Aug 27 10:22:41 Privoxy(134979584) Request: images.slashdot.org/pix.gif > Aug 27 10:22:46 Privoxy(135041024) Error: could not resolve hostname images.slashdot.org > ^^^^--- This is bad, I have no problems resolving this normally. > ^CAug 27 10:22:56 Privoxy(135163904) Info: exiting by signal 2 .. bye How old is your kernel? SCHED_ULE or SCHED_4BSD? It could be that name resolution is giving it problems because it's not thread-safe (in libc)... -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10308272003290.9892-100000>