Tag Info

New answers tagged


Maybe your dns is caching the resolution of the name and this is the reason of the diference in time of response. It's only a theory.


SELinux perhaps -- nslcd_selinux(8) -- that would help explain a difference in behaviour when running under strace (as would a process that was expecting to be setuid)


Https cannot be cached in its encrypted form. What you need is to put an SSL termination proxy in front of varnish to decrypt the traffic and then let varnish cache the content. You can use Apache to do the SSL termination by using mod_proxy and the directives proxypass and proxypassreverse inside you Vhost configuration . You can also check this two ...


There is no way to cache HTTPS traffic while it is encrypted, because the cache has no idea what is being requested, nor what is being returned in response. The only way to do this is to terminate the TLS connection at or "before" the cache, perform the caching operation on the unencrypted traffic, and then (optionally) have the cache establish another TLS ...


This document http://czerasz.com/2015/03/30/nginx-caching-tutorial/ describes that there is a process called "Cache loader". It runs only once (on startup) and loads the metadata into the memory zone. It runs in iterations until all keys are loaded.


I have just done a memcached flush so I thought I would post an example output of something that I think is working. New relic is reporting 10.4ms spent in memcached so I think it is counting multiple calls. Are you running on bare metal or virtual, if you care about speed then virtual is not the way to go ( http://redis.io/topics/benchmarks ) memcache-top ...


Nginx can load-balance and cache simultaneously, you just need to configure cache zone using proxy_cache_path directive and assign it to the particular server {} or location {} using proxy_cache. So, concluding, if using nginx as both load balancer and cache, Digital Ocean architecture looks way redundant.

Top 50 recent answers are included