Re: Varnish answering multiple incoming ports
Fredrik Nygren [EMAIL PROTECTED] writes: Better suggestions? Why split the traffic at all, if only to collect it in the same varnish instance? -- Stig Sandbeck Mathisen, Linpro ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Miscellaneous questions
In message [EMAIL PROTECTED], Mich ael S. Fischer writes: (1) Feature request: Can a knob be added to turn down the verbosity of Varnish logging? Right now on a quad-core Xeon we can service about 14k conn/s, which is good, but I wonder whether we could eke out even more performance by quelling information that we don't need to log. The shared memory log is practically free, the trick is to only pick the stuff out of it that you need to store on disk. (2) HTTP/1.1 keep-alive connection reuse: Does Varnish have the ability to reuse origin server connections (assuming they are HTTP/1.1 Keep-Alive connections)? Or, is there a strict 1:1 mapping between client-proxy connections and proxy-origin server connections? They should already be reused by default. (3) Feature request: Request hashing. It would be really cool if Varnish were able to select the origin server (in reality another Varnish proxy) by hashing the Request URI. Having this ability would improve the cache hit ratio overall where a pool of caching proxies is used. We have sort of given up on the peer-to-peer cache fetches using dedicated protocols, but if you are able to tell that another varnish is a better place to pick up something, nothing prevents you from making that a backend of this varnish and doing a pass on the request. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Miscellaneous questions
(1) Feature request: Can a knob be added to turn down the verbosity of Varnish logging? Right now on a quad-core Xeon we can service about 14k conn/s, which is good, but I wonder whether we could eke out even more performance by quelling information that we don't need to log. (2) HTTP/1.1 keep-alive connection reuse: Does Varnish have the ability to reuse origin server connections (assuming they are HTTP/1.1 Keep-Alive connections)? Or, is there a strict 1:1 mapping between client-proxy connections and proxy-origin server connections? (3) Feature request: Request hashing. It would be really cool if Varnish were able to select the origin server (in reality another Varnish proxy) by hashing the Request URI. Having this ability would improve the cache hit ratio overall where a pool of caching proxies is used. Best regards, --Michael ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Varnish answering multiple incoming ports
In message [EMAIL PROTECTED], Fredrik Nygren writes: Because of this I would like Varnish to listen for multiple incoming ports. Is it possible? I've tried this with no luck: # varnish -a localhost:81 -a localhost:82 -a localhost:83 I think the syntax is varnish -a localhost:81 localhost:82 localhost:83 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
