Thanks for this confirmation. These were my next steps anyways. I will update this post if I have any definite indications that something is amiss in userspace. Best regards, Aurélienby footplus - Nginx Mailing List - English
Hello, I'm currently investigating an issue with Linux (3.13.0), nginx (1.6.2), vmxnet3 (1.2.0.0-k-NAPI), IPv6 connections and large receive offload (LRO) enabled. The workflow we are investigating is a POST of a small file (jpg) towards a php5-fpm pool. From a network (tcpdump) point a view, it seems that when LRO is disabled on the vmxnet3 interface, all tcp packets are ack'ed correctly afby footplus - Nginx Mailing List - English
Hello, When using nginx in proxy_cache mode, and configuring the cache zone like below, it seems that the zone sometimes exceed the configured size by like 10%; I'm buffering new items at a high rate, and I'm wondering how this cache zone is cleaned up ? Is there a time-based recurring size check ? or another mechanism ? I also noticed that the cache doesn't seem to be cleaned before the cacby footplus - Nginx Mailing List - English
Hello, While doing benchmarks in a configuration using proxy_cache and proxy_cache_lock, I noticed that many requests had a duration very close to 500ms. Upon further analysis, I determined that a huge majority of these requests were actually HITs, and investigated to see where do the delay came from. I currently suspect that this particular delay come from HITs that were delayed by proxyby footplus - Nginx Mailing List - English
Thanks for your reply. I'm currently using this mechanism (small variation of yours) to work around the limitation. On every intermediate cache server, i'm using the following (whole chain is using nginx). map $upstream_cache_status $accel_expires_from_upstream_cache_status { default ""; STALE 1; UPDATING 1; }by footplus - Nginx Mailing List - English
Hello, I am currently implementing a caching proxy with many short-lived items, expiring at a specific date (Expires header set at an absolute time between 10 and 30 seconds in the future by the origin). For various reasons, my cache is multi-level (edge, intermediate 2, intermediate 1, origin) and needs to make the items expire at the edge at 2exactly the time set in the Expires header. Whenby footplus - Nginx Mailing List - English