On Mon, Apr 13, 2009 at 07:35:47PM -0400, Michael Izioumtchenko wrote: > but really, are they fast? What are Drizzle's plans about I_S?
Likely turn it into an engine, and have hooks for other plugins to provide tables. Thanks to the FRM removal and (ongoing) discovery work, this should be simple. > And the data dictionary and/or runtime memory only statistics? Both > could be useful services for any DB engine. runtime memory statistics does need some work, but it shouldn't be hard to get right. > I'd imagine an ideal statistics module to be a memory only database > engine with UNCOMMITTED READ as the only Yes - you scan the values, either computed on-fly or already stored. certainly READ UNCOMMITTED style isolation. But this is more performance schema than information schema. There is a solid case to be made that I_S tables should be consistent and READ COMMITTED (at least). > isolation level. It could also employ shared memory so people could > write risky but fast readonly All read only. write values are configuration. > clients that would forgo some locking at the expense of an occasional > clientside SEGV. Note that this wouldn't be client side, this would be *server* side as all the I_S magic has to happen in server. -- Stewart Smith _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
