To increase the speed of website you can serve static contents to clients. Static contents take less time to load so your webpage loads very fast. To store static contents you can use caching technique. In caching you can store frequently used data. Whenever someone asks for the data you can serve the data from the cache, not from the main server. There are different techniques to achieve caching. You can use Varnish or Nginx as a reverse proxy for caching content. For caching a database server you can use Redis server. Varnish and Nginx can also handle heavy traffic.<\/p>\n
Nginx<\/strong><\/span><\/p>\n Nginx is a free,open source,high performance HTTP server \u00a0and \u00a0reverse proxy server. Nginx can also act as a load balancer and caching server.<\/p>\n Nginx can proxy requests to servers that communicate using the http(s), FastCGI, SCGI, and uwsgi, or memcached protocols through separate sets of directives for each type of proxy. Whenever a user request some data nginx query the cache for data. If data is not available in cache it bypass the connection to the main backend server. The main advantage of Nginx is that it uses little resources while serving thousands of concurrent connections. Nginx does not create new thread for new connection.A single thread can serve thousand of connections. So a new user request does not have to wait. Nginx is well suited for load balancing.<\/p>\n Varnish<\/strong><\/span><\/p>\n Varnish Cache is a http accelerator which increases the speed of the site. Varnish is set up in front of a http web server to cache the contents. By using varnish we can greatly improve the speed and performance of the website.<\/p>\n Whenever a user request some content varnish fetch it from the backend server and serves it to the user. It also saves the content in the cache. So next time other user requests the same content it fetches the content from cache.It does not request the backend for the content. In this way user get the content without making connection to the main backend server. Varnish can serve thousand of concurrent users at same time while serving the cache content. Varnish prevents increasing the load at the main backend server.<\/p>\n Redis<\/strong><\/span><\/p>\n Redis is an open-source key value store that can operate as both an in-memory store and as cache. Redis is a data structure server that can be used as a database server on its own, or paired with a relational database like MySQL to speed things up. LIST,QUEUE,SETS,HASHES are used to store data. SQL like queries can not be performed on Redis.So Redis is a good choice for caching.<\/p>\n When first time page is loaded, a database is queried on the server. Redis caches the query. Next time other user loads the page the results are provided from the redis without quering the actual database. Redis implements a persistent object cache (no expiration). An object cache works by caching the SQL queries in memory which are needed to load the web page. When the data of main database server is updated,then corresponding key in th redis is invalidated. So the redis provides the updated data instead of caching the data.<\/p>\n We installed magento-2.1.0 on 3 different servers and compared the results.<\/p>\n The server configurations are as follows.<\/p>\n Os : Ubuntu 14.04 LTS<\/strong> 1. Apache2 + Magento-2.1.0<\/strong> programs<\/span>\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\u00a0version<\/span><\/strong> We used siege tool for stress testing.\u00a0We took 100, 500 and 1000 concurrent users and tested on 3 different urls for 30 seconds.<\/p>\n When you query some static pages like html Varnish perform much faster than the Nginx because of full page cache feature. Full Page Cache is not available in Magento 1.9 . With Varnish Magento 2 performs very fast even if there are 1000 concurrent users. As you can see Varnish makes a huge difference while serving the static content.<\/p>\n When you deal with authentication and session variables Nginx is better than Varnish. Varnish does not store cookie and session variables.So \u00a0Varnish could not supply cache variables. It asks backend for the data which causes to increase in response time.<\/p>\n As Varnish does not store dynamic data, Nginx works faster than the varnish. So if you hit the url for searching some contents which changes time to time Varnish can not store this data in the cache.<\/p>\n From these results you can see that Varnish performs better while serving static contents. If your website is consist of most of static contents then Varnish is the best choice for increasing the performance of your website. Varnish can also serve static content faster when there is high traffic on the website. But in case of serving dynamic content Varnish is not a good choice because Varnish fetches the content from the backend server every time someone requests a content. So if your website uses most of the time authentication, cookie and session variables Nginx is the best choice. Nginx can deal with cookies and session variables more effectively than Varnish. Varnish also lacks SSL support.<\/p>\n Next blog I will post \u00a0how to configure Varnish and Redis with Magento 2.<\/p>\n <\/p>\n IN CASE OF ANY QUERY, CONTACT US<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
\n RAM : 3 Gb<\/strong><\/p>\n
\n 2. Varnish + Apache2 + Redis-server + Magento-2.1.0<\/strong>
\n 3. Nginx + Apache2 + Redis-server + Magento-2.1.0<\/strong><\/p>\n
\n Apache2 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a02.4.7<\/strong>
\n Redis-server \u00a0 \u00a0 \u00a0 2.8.4<\/strong>
\n Varnish \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 4.0.3<\/strong>
\n Nginx \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a01.4.6<\/strong>
\n Mysql server \u00a0 \u00a0 \u00a05.6.31<\/strong>
\n php \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a07.0.9<\/strong><\/p>\nhttp:\/\/magento.example.com\/category-10\/category-11\/category-12.html?product_limit=30<\/strong><\/h4>\n
![\"ChartGo_baseurl_availability\"](\"http:\/\/cloudkul.com\/blog\/wp-content\/uploads\/2016\/08\/ChartGo_baseurl_availability.png\")
<\/a> ![\"ChartGo_baseurl_transaction\"](\"http:\/\/cloudkul.com\/blog\/wp-content\/uploads\/2016\/08\/ChartGo_baseurl_transaction.png\")
<\/a> ![\"ChartGo_baseurl_response\"](\"http:\/\/cloudkul.com\/blog\/wp-content\/uploads\/2016\/08\/ChartGo_baseurl_response.png\")
<\/a> ![\"ChartGo_baseurl_throughput\"](\"http:\/\/cloudkul.com\/blog\/wp-content\/uploads\/2016\/08\/ChartGo_baseurl_throughput.png\")
<\/a>\n<\/div>\nhttp:\/\/magento.example.com\/checkout\/cart<\/strong><\/h4>\n
<\/a> <\/a> <\/a> <\/a>\n<\/div>\nhttp:\/\/magento.example.come\/catalogsearch\/result\/?q=+product<\/strong><\/h4>\n
<\/a> <\/a> <\/a> <\/a>\n<\/div>\n