1, 2, 3.. If your site still doesn’t load, it’s obviously not a good sign for your business..
Many server owners get servers with excellent specifications and wait for magic to happen. But server specs alone, cannot guarantee fast websites.
GBs of memory and GHz of CPU go wasted, if they are not optimized to suit your business purpose. (more…)
In our role as Server administration specialists for server owners, database errors are something that that we resolve for them. A commonly reported one is the MySQL ‘Too many connections’ error. (more…)
For a website owner or a web host, a hard disk crash is one of the most upsetting things that can happen to their business. It means service downtime, loss of business and valuable time spent on data restoration.
To minimize such catastrophe, many server owners keep regular backups, and even use RAID servers. But even with these precautions, sometimes things can go for a toss when the backups also get lost in a hard disk crash.
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.
The MySQL replication team have been hard at work improving the features of MySQL replication. In this part, I’ll be talking about a few more features included in MySQL 5.5
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 the most widely used multi-user, multi-threading SQL database management system. To optimize MySQL performance, a DBA should have reasonable knowledge of MySQL system variables. This article covers the basics of MySQL server optimization. We will first discuss MySQL optimization during installation. Then we will discuss the seven most important and common system variables. Plus, a brief note on how to optimize the server using those seven variables.
We will also discuss MySQL status variables. This article would be very useful for a newbie MySQL DBA when setting up a MySQL server.
This article describes how to set up database replication in MySQL. MySQL replication allows you to have an exact copy of a database from a master server on another server (say we can call it as slave), and all updates to the database on the master server are immediately replicated to the database on the slave server so that both databases are in sync.
This is not a backup method or policy because an accidentally issued DELETE or ALTER command will also be carried out on the slave; but replication can help protect against hardware failures though.
Hire Bobcares Linux Server Administrators
Get super reliable servers and delighted customers
See how we do it!
Sometimes we may require to run multiple versions of MySQL on the same Server. This can happen if you either need to test a new MySQL release or you need a new MySQL version and you don’t want to make any changes to the existing system.
The whole idea behind this is to compile the new MySQL server with different TCP/IP ports and Unix socket files so that each one is listening on different network interfaces. Compiling in different base directories for each installation also results in separate compiled-in data directory, log file, and PID file location for each server.