On Tue, Feb 05, 2002 at 06:23:54PM -0700, David Phillips wrote:
> > Without giving away an "trade secrets", the plan is to run a lot of
> > separate MySQL server instances on a each machine (there will be
> > "many" MySQL server machines). Each user will get a MySQL server (in
> > the daemon sense, not the machine sense) all to themselves. Each
> > MySQL server will run with a different uid. This will give us the
> > ability to control the process using standard Unix process limits and
> > all that good stuff.
>
> We thought about that, but isn't that quite resource intensive?
Time will tell. It's really a matter of how much memory we allow each
MySQL to use. Ultimately, the biggest resource used is likely to be
disk space.
> Even with only a few hundred users, I don't think a single box could
> handle it. But the same box should be able to easily handle the
> same number if it was a single server.
One of the big requirements here is fine-grained control over the
environment. It's just a lot easier to do with multiple servers in our
case.
> You'd have to set each server to use very little RAM for buffers,
> which would cause a lot more disk and CPU overhead. Even when they
> are all sitting idle, they are taking up memory. Is the problem not
> as bad as I think it would be?
After things are proven one way or the other, I hope to be able to
write it up and/or present at a conference someday, since it's a very
interesting setup. And from what I've heard, not many folks are using
it.
> I think my idea for a modification makes more sense, since it better
> utilizes resources. But if that's wrong, I'd really like to know
> why.
I don't know that you're right or wrong. It has a lot to do with your
goals and the environment you're working in. We thought a lot about
each approach and eventually decided on this one for a variety of
reasons. Hopefully we'll know soon how it all works out.
Jeremy
--
Jeremy D. Zawodny, <jzawodn@stripped>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936
MySQL 3.23.41-max: up 2 days, processed 73,314,529 queries (416/sec. avg)
