Re: Concept check: iothreads addition to pthreads for MYSQL+FreeBSD.

2000-01-17 Thread Chris Sedore
On Mon, 10 Jan 2000, Chris Sedore wrote: > > > On Mon, 10 Jan 2000 [EMAIL PROTECTED] wrote: > > [...] > > > 1) Does this seem like a reasonable approach? [It _works_, and well. But > > > it tastes strongly of hack.] > > > > I'm not very fond of this approach to the problem, though it can

Re: Concept check: iothreads addition to pthreads for MYSQL+FreeBSD.

2000-01-11 Thread Jason Evans
On Tue, Jan 11, 2000 at 03:23:13PM -0800, Scott Hess wrote: > Matthew Dillon <[EMAIL PROTECTED]> wrote: > > A better solution may be to shift to FreeBSD4.0 (when it's released - > > wait for it to become good and stable), and then use the native > > linuxthreads port (/usr/ports/devel/

Re: Concept check: iothreads addition to pthreads for MYSQL+FreeBSD.

2000-01-11 Thread Scott Hess
Matthew Dillon <[EMAIL PROTECTED]> wrote: > A better solution may be to shift to FreeBSD4.0 (when it's released - > wait for it to become good and stable), and then use the native > linuxthreads port (/usr/ports/devel/linuxthreads) for FreeBSD. After a number of hours hacking around w

Re: Concept check: iothreads addition to pthreads for MYSQL+FreeBSD.

2000-01-11 Thread Richard Seaman, Jr.
On Mon, Jan 10, 2000 at 03:36:23PM -0800, Matthew Dillon wrote: > A better solution may be to shift to FreeBSD4.0 (when it's released - > wait for it to become good and stable), and then use the native > linuxthreads port (/usr/ports/devel/linuxthreads) for FreeBSD. > > The linux

Re: Concept check: iothreads addition to pthreads for MYSQL+FreeBSD.

2000-01-10 Thread Chris Sedore
On Mon, 10 Jan 2000 [EMAIL PROTECTED] wrote: [...] > > 1) Does this seem like a reasonable approach? [It _works_, and well. But > > it tastes strongly of hack.] > > I'm not very fond of this approach to the problem, though it can work, as > you note. Asynchronous I/O is in my opinion a much

Re: Concept check: iothreads addition to pthreads for MYSQL+FreeBSD.

2000-01-10 Thread Scott Hess
Patryk Zadarnowski <[EMAIL PROTECTED]> wrote: > I'm no expert on pthreads, but, if you decide to proceed with > implementing a mixed user-land/rfork pthread implementation, may I > suggest that you implement is through POSIX pthread_attr_setscope() > interfaces instead of some local extension. pth

Concept check: iothreads addition to pthreads for MYSQL+FreeBSD.

2000-01-10 Thread Michael Widenius
> "Scott" == Scott Hess <[EMAIL PROTECTED]> writes: Scott> Recently I was tasked to find a way to scale up our MYSQL server, running Scott> MYSQL3.22.15 on FreeBSD3.3. I've been testing a hardware RAID solution, Scott> and found that with 6 disks in a RAID5 configuration, the system was only

Re: Concept check: iothreads addition to pthreads for MYSQL+FreeBSD.

2000-01-10 Thread Chris Dillon
On Mon, 10 Jan 2000, Scott Hess wrote: > 4) Is there anyone willing to commit to testing my modified pthreads > library against MYSQL? [I'll be stress testing it quite heavily, of > course. It would probably also be testable against Squid with async I/O > and multithreaded Apache 2.0.] I'm wil

Re: Concept check: iothreads addition to pthreads for MYSQL+FreeBSD.

2000-01-10 Thread Alfred Perlstein
* Matthew Dillon <[EMAIL PROTECTED]> [000110 16:04] wrote: > :Recently I was tasked to find a way to scale up our MYSQL server, running > :MYSQL3.22.15 on FreeBSD3.3. I've been testing a hardware RAID solution, > :and found that with 6 disks in a RAID5 configuration, the system was only > :perhap

Re: Concept check: iothreads addition to pthreads for MYSQL+FreeBSD.

2000-01-10 Thread Matthew Dillon
:find :> linuxthreads to meet your needs at the moment. : :That's being tested in parallel. The main issue with LinuxThreads is that :we'd go from running ~25 processes on this server to running ~800. Yes, but they are rfork(RF_MEM)'d processes - they share a lot of context between them

Re: Concept check: iothreads addition to pthreads for MYSQL+FreeBSD.

2000-01-10 Thread Scott Hess
<[EMAIL PROTECTED]> wrote: > > 2) Does anyone have suggestions for a solution that will be cleaner and > > won't take man-months to implement? [Which is the redeeming quality of > > what I've got - it took me two days to zero in on a very workable > > solution.] > > Have you tried the linuxthread

Re: Concept check: iothreads addition to pthreads for MYSQL+FreeBSD.

2000-01-10 Thread Patryk Zadarnowski
> Recently I was tasked to find a way to scale up our MYSQL server, running > MYSQL3.22.15 on FreeBSD3.3. I've been testing a hardware RAID solution, > and found that with 6 disks in a RAID5 configuration, the system was only > perhaps 30% faster than when running on a single disk. [The 6 disks

Re: Concept check: iothreads addition to pthreads for MYSQL+FreeBSD.

2000-01-10 Thread John Polstra
In article <1a6101bf5bc1$4e364b20$[EMAIL PROTECTED]>, Scott Hess <[EMAIL PROTECTED]> wrote: > > I've implemented a rough fix, which is to rfork() processes which I label > "iothreads" to handle the disk I/O. The parent process running pthreads > has a socketpair() to each of the iothreads. The

Re: Concept check: iothreads addition to pthreads for MYSQL+FreeBSD.

2000-01-10 Thread jasone
On Mon, Jan 10, 2000 at 03:20:38PM -0800, Scott Hess wrote: > I've implemented a rough fix, which is to rfork() processes which I label > "iothreads" to handle the disk I/O. The parent process running pthreads > has a socketpair() to each of the iothreads. The iothreads wait for > requests on th

Re: Concept check: iothreads addition to pthreads for MYSQL+FreeBSD.

2000-01-10 Thread Matthew Dillon
:Recently I was tasked to find a way to scale up our MYSQL server, running :MYSQL3.22.15 on FreeBSD3.3. I've been testing a hardware RAID solution, :and found that with 6 disks in a RAID5 configuration, the system was only :perhaps 30% faster than when running on a single disk. [The 6 disks in t

Concept check: iothreads addition to pthreads for MYSQL+FreeBSD.

2000-01-10 Thread Scott Hess
Recently I was tasked to find a way to scale up our MYSQL server, running MYSQL3.22.15 on FreeBSD3.3. I've been testing a hardware RAID solution, and found that with 6 disks in a RAID5 configuration, the system was only perhaps 30% faster than when running on a single disk. [The 6 disks in the R