Hi!
On Apr 27, 2009, at 12:07 PM, Sean Kelly wrote:
Feature Request: Get rid of table level write locks while hacking at
MEMORY engine.
Much easier to do if it lacks Btree from its current design :)
The big issue is tossing out all of the locking code in the kernel. To
do that though... we need MyISAM and Memory to move to having their
locks in the engine code.
Cheers,
-Brian
-s
On Mon, Apr 27, 2009 at 11:51 AM, Brian Aker <[email protected]>
wrote:
Hi!
Has anyone ever done any sort of benchmarks on the B-tree indexes
on the
Memory engine? Are people using them or are they just sticking to the
default HASH indexes?
Two reasons I am asking:
1) It would be simple to improve performance for the HEAP indexes,
but the
B-tree are much more problematic.
2) Are there any outstanding users of this feature? Or is this
untested at
large?
We badly need a new memory engine, it is high on my list. We can
get a bit
more out of the current design but it would mean dropping
functionality/etc.
Cheers,
-Brian
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
--
_______________________________________________________
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
