Hi!
On Dec 19, 2008, at 9:19 AM, Tim Soderstrom wrote:
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.
It would also provide a way of creating a tiered multi-tenancy system
inside of the database. Let users pay for the bandwidth they are
using. You could also charge for the write() cost by charging for the
number of writer threads.
Tier'ing usage is probably a bad word, but when we look at how a
vendor will need to deploy in mass, I don't think you can skip. The
good news is we can skip it... or we can let you charge as you like
(so we don't really force anyone deploying into one path or the other).
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
