On Tue, Feb 7, 2012 at 11:33 AM, Marcus Eriksson <[email protected]> wrote: > basic idea is to parse SELECT-queries client side and make them use the > handler socket interface (i know drizzle doesnt support that yet, but > someone could hack that up right? :) )
The idea is great. I've heard reports of 2x or more speedups with moving the bulk of SQL parsing client side. (2x is for writes, for reads apparently up to 7x is possible.) It seems even the HandlerSocket creators are now advocating us to look at the memcache API in MySQL 5.6. It's still a preview release only, but maybe instead of integrating HandlerSocket, we could integrate one of those preview releases - it is likely where the world is going anyway. Doing that integration seems like an idea for another GSoC project :-) I've been thinking of following ideas: - integrating Spider Engine (it's a way to get transparent sharding) - integrating Galera (includes extending replication api to provide info on innodb locks held) - extending JS plugin to become a full featured "stored procedures in JavaScript" engine. - Add CALL statement to parser. - Add a way to use Execute API from within Javascript. - Assuming I will complete basic GET/POST/PUT/DELETE for HTTP JSON Server soon, extend it to also support indexing and filtering on secondary keys. - Building on CATALOG, for instance configuration facilities to map username into a specific catalog. (This is backwards / mysql compatibility for clients that cannot specify the catalog explicitly.) - Does Authorization API even support catalogs yet? Should start there if not. henrik -- [email protected] +358-40-8211286 skype: henrik.ingo irc: hingo www.openlife.cc My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
