【正文】
? Looked up by secondary key New Schema ? CREATE TABLE `guestbook_v4` ( `identifier` int(9) unsigned NOT NULL auto_increment, `user_name` varchar(16) NOT NULL default 39。39。, `photo_identifier` int(9) unsigned NOT NULL default 39。039。, `posted` timestamp NOT NULL default 39。00000000 00:00:0039。, … PRIMARY KEY (`photo_identifier`,`posted`,`identifier`), KEY `identifier` (`identifier`) ) ENGINE=InnoDB 1 row in set ( sec) Pending preads (Optimizing Disk Usage) Data pages ? Data ordered by posite key consisting of photo_identifier (FK) ? Looked up by primary key ? Very low read requests per second Pending reads / writes / Proposed Throughput not as important as number of requests Pending reads / writes / Proposed Pending reads MySQL Performance Challenges ? Finding the source of problem ? Mostly disk bound in mature systems ? Is the query cache hurting you? ? RAM addition helps dodge the bullet ? Disk striping ? Restructuring tables for optimal performance ? LD_PRELOAD_64 = /usr/lib/sparcv9/ Considerations for future growth ? SQLite? ? File system? ? PostgreSQL? ? Make application better and optimize tables? Things to remember ? Know the problem ? Know your application ? Know your storage engine ? Know your requirements ? Know your budget Questions?