[Varnish] #792: Bandwidth management / rate-limiting

thebog thebog at gmail.com
Thu Oct 7 20:25:14 CEST 2010


Another, equally important, use for this is protecting against "attacks".

I remember once we had a proxy against our site that did prefetch
(yes, somebody has written such a bad boy, and yes, they are called
M$).
They used 100 Mbit/s filling thousands of articles that their cache
thought might get read again :)

Ab

On Thu, Oct 7, 2010 at 1:29 PM, Varnish <varnish-bugs at varnish-cache.org> wrote:
> #792: Bandwidth management / rate-limiting
> -------------------------+--------------------------------------------------
>  Reporter:  tmagnien     |       Owner:  phk
>     Type:  enhancement  |      Status:  new
>  Priority:  normal       |   Milestone:
> Component:  varnishd     |     Version:  trunk
>  Severity:  normal       |    Keywords:  bandwidth rate-limit
> -------------------------+--------------------------------------------------
>
> Comment(by tmagnien):
>
>  After rereading, I think I should use TIM_real() to get timestamp before
>  and after write operation to take into account the time used for sending
>  data, e.g. : sleep(1 - write_duration). This would allow for a more
>  precise bandwidth management.
>
> --
> Ticket URL: <http://varnish-cache.org/trac/ticket/792#comment:1>
> Varnish <http://varnish-cache.org/>
> The Varnish HTTP Accelerator
>
> _______________________________________________
> varnish-bugs mailing list
> varnish-bugs at varnish-cache.org
> http://lists.varnish-cache.org/mailman/listinfo/varnish-bugs
>




More information about the varnish-bugs mailing list