Hi!
Lets figure out a memory policy first. I talked to Jay about this for
a bit today. What I would like to do is sit down at OSCON and write up
a plan for how to tackle memory.
We have (at a least):
1) Short lived, per query.
2) Medium lived, per login session
3) Forever
We also have the issue that some things, like Tables, are not per
session and are cached.
I would like to define these out, and create a strategy that is
written down and someone and go to when they ask "how do I allocate
memory?"
And everything should be error checked/type checked.
Until we have a plan though, lets just clean up what we have to make
it a bit easier to deal with when we have a plan.
Cheers,
-Brian
On Jul 11, 2008, at 6:36 AM, Stewart Smith wrote:
On Fri, 2008-07-11 at 12:28 +0100, David LP Travel wrote:
Original 1990ties MySQL allocation always was per query on a stack.
And
when the query finished you reset the stack.
Very fast and very simple. When we added things like stored
procedures
etc that way broke. It looks like drizzle could go back to the
original
way...
/me cheers "talloc! talloc!"
:)
--
Stewart Smith ([EMAIL PROTECTED])
http://www.flamingspork.com/
_______________________________________________
Drizzle mailing list
[EMAIL PROTECTED]
http://lists.tangent.org/mailman/listinfo/drizzle
--
_______________________________________________________
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
