As discussed earlier in our MySQL Performance series, the InnoDB storage engine is designed to be a high-performance database for very large datasets. The row-locking technique it uses allows for many read and write requests to occur on a single table concurrently. This is a vast improvement in speed over traditional Continue reading “MySQL Performance: InnoDB Buffers & Directives”
The majority of work needed when adjusting the MySQL server is editing the applicable directives within a MySQL configuration file. There are multiple, optional configuration files that MySQL looks for when starting up. They are read in the following order: Continue reading “MySQL Performance: System Configuration File & Routine Maintenance”
As we explored in our previous article of our MySQL Perfomance Series: MySQL vs. MariaDB there are very few downsides to using MariaDB over standard MySQL. Our high-availbility MariaDBs have proven itself to be a worthy successor with easily migitated drawbacks. As the last article in our series we will focus on upgrading to various MySQL and MariaDB version on the following servers:
- MySQL to MariaDB on CentOS 6/7 with cPanel
- MySQL to MariaDB on CentOS 7 with Plesk Onyx 17
- MySQL 5.1-5.5 to MariaDB 5.5 on CentOS 6
- MariaDB 5.5 to MariaDB 10.0 on CentOS 6
A major factor in database performance is the storage engine used by the database, and more specifically, its tables. Different storage engines provide better performance in one situation over another. For general use, there are two contenders to be considered. These are MyISAM, which is the default MySQL storage engine, or InnoDB, which is an alternative engine built-in to MySQL intended for high-performance databases. Before we can understand the difference between the two storage engines, we need to understand the term “locking.” Continue reading “MySQL Performance: MyISAM vs InnoDB”
Every MySQL backed application can benefit from a finely tuned database server. The Liquid Web Heroic Support team has encountered numerous situations over the years where some minor adjustments have made a world of difference in website and application performance. In this series of articles, we have outlined some of the more common recommendations that have had the largest impact on performance. Continue reading “MySQL Performance: Identifying Long Queries”
The LAMP stack is the foundation for Linux hosted websites is the Linux, Apache, MySQL and PHP (LAMP) software stack.
The Four Layers of a LAMP Stack
Linux based web servers consist of four software components. These components, arranged in layers supporting one another, make up the software stack. Websites and Web Applications run on top of this underlying stack. The common software components that make up a traditional LAMP stack are: Continue reading “What is a LAMP stack?”
When you create a website on Cloud Sites control panel using Linux technology, setting up a database for that site will use phpMyAdmin as the MariaDB database handler for your site. If you haven’t set up a database in Cloud Sites, see our article Creating a Database in Cloud Sites.
The Usage tab in your Cloud Sites control panel provides information on the amount of bandwidth, disk space and database usage for your sites. Your Cloud Sites control panel includes 50GB of disk space and 500GB of bandwidth. You can log into your Liquid Web Cloud Sites account to view the current charges for additional space and bandwidth use.
View Resource Usage Data
To help you keep track of these metrics, the Usage tab gives you a breakdown of your usage so that you can adjust accordingly and avoid any issues.
Continue reading “Checking Resource Usage in Cloud Sites”