Use Azure to solve "look for" disk IO problem

Look for it (zzk.cnblogs.com) is our site search products, is a disk IO-intensive (Read and write index file) application, since the migration to Aliyun has been the cloud server's disk IO problems, and Aliyun did not provide an alternative solution.

Because of this problem, look for to see unexpectedly become our whole station response speed the slowest application. People are forced out, although Aliyun is trying to solve the problem of disk IO, but we can no longer have the heart to let users endure "look for" bad response speed. So we found a compromise solution-moving the Indexing Service we looked for to the virtual machine in Azure.

This migration was completed today. After the migration to look for the deployment of this: zzk.cnblogs.com site or run on the Ali server, the latter Indexing Service running on the azure virtual machine, the user search zzk.cnblogs.com will remotely invoke Azure on the " Look for the Indexing Service, so the disk IO operations for read and write indexing are all on azure. From today's observation, look for the response speed significantly improved.

This blog post was written not to bash Aliyun's disk IO, nor to compliment Azure. Aliyun and Azure are both resources, and each resource has its limitations. What we share is how to solve the problems we currently face with the highest performance we think.

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/Servers/cloud-computing/