proxy_cache

Anatoli Marinov toli at webforge.bg
Thu Jan 12 12:40:15 UTC 2012


Yes I can pre-fetch the sets but it also is an workaround and it 
requires time for pre-fetching.
Currently I am working to get this approach on.

On 01/12/2012 02:30 PM, António P. P. Almeida wrote:
> On 12 Jan 2012 09h49 WET, toli at webforge.bg wrote:
>
>    
>> I know this configuration variable. It has been added by Maxim last
>> mouth in unstable (as i remembered but I am not absolutely sure). It
>> seem to be a workaround and will not solve the problem. I think it
>> is unusable.
>>
>> If we use it for the same case: In first 1 second A receives 1000
>> requests. Only 1 request will be send to B, for first request that A
>> receives. The others 999 will wait for example 5 seconds. The link
>> btw A and B is 1 MB per second and for 5 seconds A may receive 5 MB
>> of data, so after 5 seconds 999 requests will be sent to B.
>>
>> Is it right?
>>
>>      
> Why don't use incron or other inotify based tool to pre-fetch the
> assets? There's also http://wiki.nginx.org/HttpProxyModule#proxy_store
> which IMO seems more adequate to your setup.
>
> Other option is to use something like auth_request with a script or
> the embedded Lua (http://wiki.nginx.org/HttpLuaModule) or Perl modules
> (https://github.com/zzzcpan/nginx-perl) and do some scripting.
>
> --- appa
>
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
>    



More information about the nginx-devel mailing list