![]() ![]() One of the first things I noticed was that it took over 1 second to generate the main home page. ![]() Caching, even at the reverse proxy/load balancer level, can greatly improve performance.Īs an example, last year I took on the task of performance tuning a website that was loading slowly. There are potentially multiple caches between the web browser and the application server: the client’s browser cache, intermediary caches, content delivery networks (CDNs), and the load balancer or reverse proxy sitting in front of the application servers. This improves performance as the content cache is closer to the client, and more efficiently uses the application servers because they don’t have to do the work of generating pages from scratch each time. If a client requests content that the cache has stored, it returns the content directly without contacting the origin server. OverviewĪ content cache sits in between a client and an “origin server”, and saves copies of all the content it sees. This blog post covers techniques that can help both novice and advanced users see better performance from utilizing the content cache features included in NGINX and NGINX Plus. One such example is by implementing and optimizing caching in your application stack. Code quality and infrastructure are of course critical, but in many cases you can make vast improvements to the end user experience of your application by focusing on some very basic application delivery techniques. The process of making your application or web site perform better, however, is not always clear. We all know that the performance of applications and web sites is a critical factor in their success. ![]()
0 Comments
Leave a Reply. |