Most of us are familiar with LAMP, the most popular free/open source solution stack in use today. There is an, not as popular, alternative that database intensive site owners might be interested in: LAIP. While LAMP stands for Linux, Apache, MySQL and PHP; LAIP swaps out Oracle’s MySQL server for IBM’s Informix database server.
There have been many advancements in MySQL 5.5, a majority of them have been towards improving performance and scalability. InnoDB is now the default storage engine, which provides higher levels of performance and reliability than MyISAM. InnoDB 1.1 that is, a rearchitected InnoDB with many performance and scalability features over and above the built-in InnoDB in 5.1 and before. The industry switch from increasing CPU clock speed, to increasing the number of cores, left MySQL with a number of bottlenecks that prevented it from taking advantage of the extra processing cycles made available. This is no longer the case with MySQL 5.5, which takes full advantage of SMP systems. One area however, that I feel will be of particular interest to web hosts, are the advances in database replication in MySQL 5.5.
MySQL is an important service in the Web-Hosting industry. Almost 80% of websites on the Internet are database driven. In a shared hosting environment, the availability of this service is critical.
Many times, I have come across the problem of some particular database query taking more time to execute or using more resources. Eventually the result is high load on the server. This can be due to a sequential query to select a particular value from a large table which is not optimized.
A simple approach can be adopted to find the query and table involved. To do this you can enable slow query logging.