Azure WebApp Efficiency Tip
Introduction
Unoptimized photographs, Javascript Points, an excessive amount of flash content material, extreme HTTP requests, not making use of caching methods, unclean code, not utilizing gZip compression, too many adverts, not utilizing a CDN Service, unhealthy internet hosting…
Aside from the above prime 10 causes an internet site may be gradual, there’s one more reason, “Unhealthy Internet hosting Configuration”, that’s more often than not the problem behind all.
How does this occur?
More often than not underneath the stress of timelines of the mission, builders create sources haphazardly and don’t cater to the rules correctly. Typically prototypes develop into tasks, they usually use the identical set of sources they used whereas demoing.
Impact on Tasks?
Easy, delays occur. To research the unhealthy configurations, generally the blame is on builders that they’ve written code that isn’t performing. Whereas the issue lies within the infrastructure itself. Builders spend plenty of time analyzing database queries, picture optimizations, and code optimizations, however generally it is of no use.
What to do then?
Let’s take a look at a situation. Say there’s a mission that’s utilizing MS Azure Net APP Service and MSSql Database to retailer knowledge. When each sources had been created on Azure, they created the app service on South East Asia and a database in South Central US.
When the end-user makes a request, the request goes to the southeast Asia server, which then routes to the south-central US server to get again knowledge. It’ll then route again to South East Asia Server after which to the end-user. Lengthy journey it’s, yeah.
The very first thing to think about is that every one sources for a similar mission are in the identical Azure area.
Some folks recommend Geo-replication, Load balancing, and stuff. However why so as to add additional price when the beast may be tamed at much less price.
Geo-Replication and Load balancing are for situations when the visitors load exceeds your server limitation. Not each situation suits these.
One other factor to think about is when you desire to maintain the sources in the identical subscription as effectively for manageability and stop unseen DNS routing underneath the hood.
This above tip is golden and in case your configurations are incorrect, this may improve your web site efficiency triple-fold.