Hi!
On Jul 13, 2008, at 12:29 AM, Antony T Curtis wrote:
20,000 tables, definition stored in memory as simple SQL statements,
plucking number out of sky, lets assume 2000 chars average for table
definition. That gives us about 40 Mb of memory
What happens when the DB is up for a year or two?
Take for instance a shop who builds daily tables, works on them, and
then drops them. One load? Awesome... no problem.
Over time thought?
Practical upshot - all the INFORMATION_SCHEMA operations will be
quicker and won't need to hit the disk at all.
I think we can get around this anyway. Current design is FUBAR.
What about dropping the central cache, keeping table info around and
just using your async communication method to flush?
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
