Errors to note in three cloud migrations

Today, in the IT industry, cloud computing is fast becoming a "favor". It companies are chasing, but they also encounter many brands like the cloud and cloud platforms when migrating to the cloud platform , as well as the way in which migration would be better. However, most enterprises , in an effort to take the cloud platform as their operating system, generally does not consider performance issues when migrating, which causes them to make serious mistakes and lose significant performance. We should know as early as possible, to avoid it as soon as possible, the rush to the cloud platform may make it application run is very painful.

There are three common mistakes:

Forcibly porting code without localized modifications based on the cloud platform. Do not consider I/O scheduling issues. Network latency is not considered.

Many IT companies often do not have to modify the code to make the platform to migrate the code, these people think on the cloud platform and on the local system as arbitrary processing of those C + + code, in fact, this is not feasible.

In fact, when porting code between different platforms, you need to localize and optimize, not just the cloud platform, IaaS or PAAs. Those cloud-computing providers often boast that they can achieve the perfect portability of a to a-level, but in fact, you have to do a lot of extra work to achieve the a-a level of performance.

I/O scheduling problem is also an optimization problem, you need to specifically optimize the I/O underlying system scheduling functions. Remember that the I/O problem differs from the elasticity of the cloud platform and does not automatically adjust when the processor is saturated. The key to I/O problems is the need to access the original I/O system in the most efficient manner. Some cloud service providers can provide I/O scheduling optimization, others can not.

The network latency problem is similar. The Internet cannot always provide a stable performance, so you have to take into account the overall performance model in the cloud environment and consider the problem of network latency. If there are delays in your business that can cause big problems, don't migrate to the cloud.

Also, don't forget that network latency occurs when communication occurs between different systems in the cloud environment. I find this often overlooked, and in practice such delays are difficult to monitor, and more difficult to understand, especially if you are not exposed to the underlying physical system, and you need to work with the cloud provider to do this.

Original address: http://www.infoworld.com/d/cloud-computing/heads-3-cloud-performance-gotchas-173073

"Edit Recommendation"

Experts uncover 10 common questions about cloud computing ten risks in public cloud computing and how to deal with it today's cloud computing can support any application? Analysis of three Sins of cloud computing: Offline fault privacy and security "responsible editor: Jalon TEL: (010) 68476606"