Summary of five tips for locating database performance issues

The use of "E-mentor Network" database will become sluggish with the growth of business and data, when the database performance becomes worse, the technical staff can often reverse the situation, the following shows you a few technicians using commonly used to discriminate database performance problem method

1. Vertical upgrading of infrastructure facilities. Investing more computing resources is the usual way to solve problems, but this approach does not necessarily make performance gains. Even if the right pool of resources is expanded, the amount of resources that can be effectively utilized is still limited. Adding infrastructure is difficult for databases that are hosted on physical devices, but virtual or cloud-hosted databases are very easy to provision compute resources.

2, horizontal expansion. Some databases that resemble clustered MySQL are extensible. However, the actual size limitations of the cluster or the requirements for partitioning technology affect application consistency or reliability. The cluster also requires a change in System management mode to execute a new data protection plan.

3. Activate the archive. Sometimes it is possible to maintain performance by archiving older data. Archiving often means that some data is no longer completely useful, but today there are hybrid column compression options like Rainstor or Oracle that can handle static-related data. As data becomes more static and compressed, the performance of analytic queries on these archived data actually increases.

4, using Flash speed. Flash memory is one of the most popular performance solutions. When deployed strategically, it can accelerate far more than just a database. One of the great advantages of flash acceleration is that flash memory is transparent to the database system. Flash memory can be used as a server or storage cache (such as Fusion-io) or solid state drives, and can also be placed on the network, such as astute VISX all-flash storage. Some vendors, such as Pernixdata, pooled server flash into their own storage tiers, blurring the boundaries of storage and servers. Flash memory is still very expensive, and some solutions are optimized for read IO only, and are not necessarily able to eliminate current database bottlenecks.

5, Database engine upgrade. An interesting new way to optimize database performance is to upgrade the database internal engine. For example, for popular MySQL and MongoDB databases, you can find a high-performance (free, open-source) version of the internal engine to replace from Tokutek. The process of replacing the database engine is transparent to the application and does not require any changes to the infrastructure.

The additional benefit is that database I/O operations are naturally optimized together to give full play to the benefits of flash due to the updated mechanism of database indexing and writing data.

Often in the face of critical performance degradation, IT departments are forced to make huge investments that lack reliable returns. To avoid more and more infrastructure performance issues in the future, be mindful of the optimization options listed above. It is a better practice to put these options first to proactively explore, and you will be able to avoid database performance issues. want to learn more database Tutorial knowledge can be logged in E Mentor network.

Summary of five tips for locating database performance issues