Performance improvement and php code on a google maps project

Analyze and improve performance of an php/mysql google maps application. With growing data to display on screen current application has become too slow reading from the Mysql database and updating the map, almost to a point of nothing is being displayed at all. You must therefore be able to analyse the current use of the MYSQL database and update/improve the performance of the php database searches. Furthermore the coding must be improved. See below Other information I see that in the index page, it tries to load all data from place and multimedia, which comes to about 11000+ records. I dont think this is going to workout any ways. The map mashup uses very old google implementation. ...no sql abstraction or framework is used, whole of the code is handwritten. With a lot of places having checking affected_rows after issuing a select query. Normally we check the num_rows (mysql_num_rows) after issuing a select query. and check mysql_affected_rows after an update to make sure the update went through. Further information: in the [login to view URL] ( which is loaded to show the main page ), the tables place and multimedia are joined with a short_name ( as far as i remember, need to check back ) and no other constraints and an order by also. This will load the mysql system to use a table scan and eventually use a file sort. Also all the tables you provided were either MyISAM or InnoDB, could not find any ndbcluster tables, means the application does not use cluster facilities, and sits on a single db node, which worsens the problems. And in the [login to view URL] itelf, a javascript parseable string with delimiters like '++++/@@@' are created and passed to the onload event of the body, creating about 350KB single string to be parsed using javascript. In such cases I normally use php function json_encode ([login to view URL]), and pass the json string to javascript such that parsing can be real low memory intensive. But for google maps where we are adding points which are clickable to show messages or popups, much lighter would be to create an xml file with the kml dtd and let google handle rendering of the marks. Finally: -Code updated to newest API -Cluttering on map added/allowed