Tim Soderstrom wrote:
> On Dec 19, 2008, at 10:29 AM, Brian Aker wrote:
>> On Dec 19, 2008, at 1:33 AM, Roy Lyseng wrote:
>>> Is it not easier to limit that on a tablespace level?
>>> Assign one tablespace per user with some fixed maximum disk space.
>>> Make sure that a user only sees the database objects (schemata,
>>> tables, tablespaces, ...) that (s)he has access to. (hopefully this
>>> is already implemented in MySQL/Drizzle - I did not check...)
>> Except for the disk space limitations, I am 90% sure I could write a
>> module that did this today. The only thing I could not control is the
>> Innodb buffer size... for that I believe I need Innodb to be able to
>> handle multiple contexts.
> I'd say controlling the buffer pool is more important really. Without
> that, another user can thrash the buffer pool with a few silly queries
> and make it painful for the rest of the users on the system.
For even better control, fire up a Solaris zone and a database instance
inside it. Then you can control IP, disk quota, memory usage, CPU, etc,
and probably simpler than partitioning the database server...