One of the limits we enforce is the amount of pressure you can put on the MySQL database server ( also called MySQL overloading. we force it to ensure that websites run as fast as they can.
What does MySQL overloading mean?
Majority of dynamic websites are using a database to store dynamic data (account, products, comments, posts etc.). That data is stored on database servers. your website is able to interact with it to see and modify the data stored on these servers.
Database servers need to word to provide and change the data you supply through it. A lot of dynamic websites have to carry out a lot of queries for a requested page, so analogously it needs to be fast.
To keep the server load low on database serer, we often check the load on the server itself. If we decide that the load is too high and the performance of the website is reduced, we suspend the accounts using the most power for 24 hours.
This ensures that the load will stay low and the speed of your websites high.
My website is overloading the server - how?
A lot of factors can overload the database. A few common issues are:
- Your website received a high amount of hits, resulting in a lot of queries being executed.
- Your code might be executing multiple queries for each request
- The queries you execute are taking high amounts of processing power to complete. Queries which manage a lot of data, have complicated subqueries or joints, improperly used indexes can put extreme amounts of pressure on a database.
- Some of the database queries you execute take a lot of processing power to execute. Queries which process a lot of data, have complex subqueries and joins, or which just don’t use indexes properly, can put a lot of strain on a database.
How can I reduce my database load?
If you’re using exiting software and aren’t writing the queries by yourself, there are a few tips that could help you minimise your database usage
- Delete needless plugins and scripts from our website
- Utilise caching on your website, because the data that is used most frequently won’t be retrieved every time that a request is made
If you’re writing the queries yourself you should look at a few of these tips to help you with optimisation:
- Ensure that only 1 database per connection is created, and it’s used for all queries. Reusing it is simply faster and lighter than creating a new database every time.
- Avoid running large database jobs. Web hosting server are optimized for light, constant usage rather than performing big requests.