Redirect on specific threshold !!

shahzaib shahzaib shahzaib.cb at
Mon Jun 15 07:07:18 UTC 2015


   Thanks for the help guys. Regarding @ryd994 suggestion, the reason we
don't want to deploy this structure is that the Caching node will have to
respond for each client's request and even it will be only doing proxy for
most of the requests(without caching them), high i/o will still be required
to serve the big proxy request(700MB mp4) to the user and that way caching
node will eventually become the bottleneck between user and storage node,
isn't it ?

@steve thanks for tmpfs point. but we're using caching node with 1TB+ SSD
storage and will prefer SSD  cache over RAM(though RAM is faster but not as
big as SSD).

Using redirect URL we believe would be only pointing specific requests
towards the cachind node and than this node will fetch requested file using


On Mon, Jun 15, 2015 at 9:13 AM, ryd994 <ryd994 at> wrote:

> Does a nginx reverse proxy with cache fit you need?
> Client -> Caching server (with SSD and nginx proxy cache configured) ->
> Storage server(s) (Slow)
> You can add even more storage server by utilizing nginx upstream module.
> On Sun, Jun 14, 2015 at 1:12 PM shahzaib shahzaib <shahzaib.cb at>
> wrote:
>> Hi,
>>    We're using Nginx to serve videos on one of our Storage
>> server(contains mp4 videos) and due to high amount of requests we're
>> planning to have a separate caching Node based on Fast SSD drives to serve
>> "Hot" content in order to reduce load from Storage. We're planning to have
>> following method for caching :
>> If there are exceeding 1K requests for
>> , nginx should  construct a Redirect URL for rest of the requests related
>> to test.mp4 i.e and entertain the rest
>> of requests for test.mp4 from Caching Node while long tail would still be
>> served from storage.
>> So, can we achieve this approach with nginx or other like varnish ?
>> Thanks in advance.
>> Regards.
>> Shahzaib
>> _______________________________________________
>> nginx mailing list
>> nginx at
> _______________________________________________
> nginx mailing list
> nginx at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the nginx mailing list