Re: [varnish] renaming varnish concepts...

In message e9dd9378-1dae-4077-a0c6-149dbac0c...@digitalmarbles.com, Ricardo N ewbery writes: On Jan 28, 2009, at 4:19 AM, Poul-Henning Kamp wrote: In message 768C2A99-6D24-4D6F- b324-25e13cfbe...@digitalmarbles.com, Ricardo N ewbery writes: Cool... so why do you figure that backwards

Re: [+] Re: Breaking Varnish

, to disable the (effectively unused) per source-IP statistics. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: Breaking Varnish

lose the cache, which is obviously not particularly desirable under heavy load. Persistent storage coming up in version 2.1 :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never

Re: [varnish] renaming varnish concepts...

. With the new code, which will possibly be in 2.0.3, you can express it sensibly: purge req.url ~ some_regexp req.http.host ~ some other regexp But we cannot do an object lookup, so we can not reclaim the storage of those objects immediately. -- Poul-Henning Kamp | UNIX since Zilog Zeus

Re: Cacheability - changed in Varnish 2?

(or vice versa). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: [varnish] Re: Cacheability - changed in Varnish 2?

. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | 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

Re: Cacheability - changed in Varnish 2?

In message 49817d5c.10...@giraffen.dk, Anton Stonor writes: Poul-Henning Kamp wrote: As far as I can tell, a zero TTL (number after RFC) can only happen here if your default_ttl parameter is set to zero, OR if there is clock-skew between the varnish machine and the backend machine. Right

Re: Cacheability - changed in Varnish 2?

In message 49818470.10...@giraffen.dk, Anton Stonor writes: Poul-Henning Kamp wrote: I hope we don't ship varnish that way on any platforms, the default ttl should be 120 seconds... No, the 0 default ttl comes from this one: http://pypi.python.org/pypi/plone.recipe.varnish From

Re: Panic message: Assert error in exp_timer(), cache_expire.c line 303

I think I fixed this in r3565. Poul-Henning In message 200902012032.00280.ottol...@web.de, Sascha Ottolski writes: Am Mittwoch 28 Januar 2009 10:52:47 schrieb Poul-Henning Kamp: In message 200901260917.45223.ottol...@web.de, Sascha Ottolski writes: Assert error in exp_timer(), cache_expire.c

Re: is 2.0.2 not as efficient as 1.1.2 was?

) dispenses with the need to store the hash-string so theory could be tested. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained

Re: Understanding nukes the expiration thread

, the object closest to expiring. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: Should we keep the man pages?

the overall workings and VCL in particular, manpages suffer badly from the inability to include sensible illustrations. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice

Re: Default behaviour with regards to Cache-Control

control. Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: Default behaviour with regards to Cache-Control

In message loom.20090212t090929-...@post.gmane.org, Ole Laursen writes: Poul-Henning Kamp p...@... writes: I looked up private here http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html and it says Indicates that all or part of the response message is intended for a single user

Re: Default behaviour with regards to Cache-Control

In message loom.20090212t102450-...@post.gmane.org, Ole Laursen writes: Poul-Henning Kamp p...@... writes: We don't consider varnish a shared cache in the RFC2616 sense of the concept, because the varnish instance is fully under the control of the servers administrator, and should therefore

Re: Varnish and mp3 streaming on demand

in temporary (malloc) or persistent (disk) storage. With some extra work, this will allow pass to become streaming. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice

Re: Varnish and mp3 streaming on demand

In message loom.20090213t100923-...@post.gmane.org, Ole Laursen writes: Poul-Henning Kamp p...@... writes: This is necessary to be able to decide, per object, if it should be stored in temporary (malloc) or persistent (disk) storage. With some extra work, this will allow pass to become

Man at Work

if some of you have time to run -trunk a bit every so often to help weed out the bugs. Poul-Henning [1] Yes, I watch too much Colbert Report. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never

Re: varnishlog output column meaning

be the case. The 'b' means backend transaction, and 'c' client side transaction. 7 VCL_return c pass 10 BackendOpen b default 127.0.0.1 57141 0.0.0.0 3000 7 Backend c 10 default default 10 TxRequestb HEAD -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org

Re: Putting the site in maintenance mode?

vcl.load maint filename When you want to go into maintenance mode, you switch to that VCL, using vcl.use maint when you want to get back to production, you switch back to your normal VCL with vcl.use boot -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP

Re: Handling graced objects between varnish servers.

-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | 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

Re: Handling graced objects between varnish servers.

In message b80ebd14-fa1b-40c5-8243-1c5c2edb1...@funnyordie.com, Jeff Anderson writes: Is there a way to tell or flag set if the fetched object is a graced object? In VCL you can tell by the negative ttl. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP

Re: Different TTLs dependent upon req.http.host?

In message 49fe9576.7080...@d0pefish.de, Peter Hinse writes: No idea? User-defined variables do not work, is there any trick I can use to handle requests to xi.example.com differently? Which version are you running ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org

Re: Cookie validation with varnish?

to allow such stuff to be done, but right now my focus is on persistent storage. Poul-Henning PS: We are happy to hand out wiki bits (drop me an email), so people can add ideas to our shopping list wiki page: http://varnish.projects.linpro.no/wiki/PostTwoShoppingList -- Poul-Henning Kamp

Re: 'Write error' messages in varnishlog

receiving the entire contents. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: Poor #requests/second performance

to precreate a suitable number of threads to avoid dropped requests while varnish ramps up. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained

Re: Poor #requests/second performance

are OK). Threads not created should be zero. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: Poor #requests/second performance

(longest request) No idea... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: Problems getting Varnish to cache certain things

matching request to the backend. A restart clears this. If I recall correctly, one of the triggers is using 'pass' inside vcl_hit or vcl_fetch. Only pass in vcl_fetch will create a hit for pass object. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC

Re: Problems getting Varnish to cache certain things

, is to avoid serializing clients on objects that cannot be cached. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Time for a Varnish user meeting ?

to try to organize something ? Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: Problems getting Varnish to cache certain things

-for-pass behaviour. The object will not be marked as hit-for-pass if you do that, but the resulting behaviour is the same, so unless you inspect stats, you cannot tell the difference. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD

Re: Apache DoS - is Varnish affected?

) will never even see these connections in the first place. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: Thread memory allocation question

-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | 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

Re: varnish caching problem

In message f8baa10ae2544b3d8f60eb96a78dc...@sridharraju, Sridhar writes: My Varnish is not showing cache hits while I run from firefox. Check if you send cookies, by default cookies diables caching. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since

Re: Welcome back from vacation!

have minimal trouble getting there. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: abnormally high load?

And yes, wouldn't it have been nice if POSIX had included a way to see how many pages the kernel know you use ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can

Re: Thread pools

-90% idle CPUs. Have you played a bit with varnihshist ? I suspect that may be the most sensitive, if crude, indicator of overall performance we can offer. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since

Re: Varnish, long lived cache and purge on change

to 104 bytes. I seem to recall that the locking is benign. Probably the more interesting question is how aggressive you want it to be: if it is too militant, it will cause a lot of needless disk activity. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since

Re: Varnish, long lived cache and purge on change

In message 2837.1250697...@critter.freebsd.dk, Poul-Henning Kamp writes: In message 4a8bb076.50...@gmail.com, Rob S writes: Just to follow up to myself after trying to hack up a solution in -trunk: I seem to recall that the locking is benign. Make that Mostly benign :-) Probably the more

Re: bad national characters in synthetic

Any sugestions? File a bugreport. Use ...; syntax until I have time to look at it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately

Raising funds for developing Varnish

-Henning Kamp -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | 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

Re: many workers threads failed with EAGAIN

In message dcccdf790908311636g39bbf036icdc66405e46aa...@mail.gmail.com, David Birdsong writes: What does your responstimes look like in varnishhist ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3

Re: if obj.status == 50[1|2|3|x] - reissue request on next backend(s)

= better_one; } else { set req.backend = normal_one } -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately

Re: purging

from the list for reference counting reasons) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: varnish redundancy

-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | 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

Re: req.xid semantics?

value on startup, and each request gets a unique value. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: client keepalive on high trafic site

latency responses, only 10%cpu usage on server, load around 1-2) Why don't you restrict connection: close to non-IE6 then ? You can test the User-Agent header in your VCL code -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer

Re: performance scalability of a multi-core

have been floated, how to deal better with that, but no really good idea has been found yet. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately

Re: Sub-second granularity logs

resolution, just find the right printf and fix the format. Getting a timespec is just as expensive as getting a time_t, because time(2) simply calls clock_gettime(2) under your feet. Which shmrecord are we talking about ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org

Re: smart health check response?

In message dcccdf790909132251o360dd2f1if10619325fb87...@mail.gmail.com, David Birdsong writes: ...are any of the stats available inside vcl_error? Not directly, but you can relatively easily get your hands on them if you use inline C-code. Poul-Henning -- Poul-Henning Kamp | UNIX since

travel: eurobsdcon2009 and vug1

) Wednesday I'll hang out with an old friend and thursday I'll start to dig myself out of the heaps which have accumulated. See you there... Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe

Re: Varnish User Group Meeting 2009-09

of getting from Cambridge to London out, working on that right now. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: Varnish User Group Meeting 2009-09

. Yes, I have reached the same conclusion. I think I'll aim for the 0715 from cambridge, that should have me at Pimlico around 0830. Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe

VUG1 meeting resport

Varnish :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | 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

Re: PIPE asserts

other status code than 503 which you might prefer) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: POST body logging

In message 20091002212608.gd19...@digdug.corp.631h.metaweb.com, Niall O'Higgi ns writes: Hi all, I'm trying to get Varnish to log POST body contents. Sorry, we have no code to support that presently. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP

Re: Panic message: Assert error in VSL(), shmlog.c line 157

___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc --===1052186233==-- -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD

Re: call a sub function and return

obj.ttl = 10m; #return (0); } if (req.url ~ ^/def/* { set obj.ttl = 30s; } } It's not clear from you example what you would use the return for, but you can simulate it, but putting you return value in a header instead -- Poul-Henning Kamp | UNIX since Zilog Zeus

Re: call a sub function and return

) { } elseif (bar) { } elseif (foomble) { } else { } -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained

Re: Yahoo! Traffic Server

... :-) Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Back from the dea^H^H^Hsoul-less

Lenovo is supposed to reply. And then it's back to hacking varnish... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained

Re: Back from the dea^H^H^Hsoul-less

In message 002c01ca5da3$77a93230$66fb96...@paulissen@qbell.nl, Henry Pauliss en writes: Windows-refund case?=BF? Did i miss something? http://phk.freebsd.dk/MicrosoftSkat/ You should be able to read it :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP

Re: Varnish virtual memory usage

. Only on 32bit systems is there any reason to be concerned about VM-space used. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained

Re: Benchmarks [was: Yahoo! Traffic Server]

the way to do that kind of benchmark was to send a twitter message like: Hehe, looks like Jessica Biels bikini straps snapped (http...) :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never

Worker thread stack size

numbers of worker threads squeezed into the address-space. I have no idea how much stack-space a worker thread normally uses, so no guidance is given, and we default to the system default. Fixes #572 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since

Re: Fwd: Cache utilization?

moved objects = I guess what you call kill activity is the same as nuked objects? Correct, you seem to have plenty cache space. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute

Re: varnish bottleneck?

That is correct. If you use pipe, the TCP connection turns into a straight pipe where bytes are moved from client to server, without further inspection, until either side closes the TCP connection. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since

Re: varnish bottleneck?

In message 4b0f276a.9000...@gmail.com, ll writes: if (req.request == POST){ pipe; } Use pass, not pipe. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can

Re: vcl_error synthetic escape chars

-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | 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

Re: only 503s after a few hours (trunk-4384)

as many filedescriptors as it needs. Use whatever means your kernel has to change this number, possibly ulimit(1) or similar. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute

Re: varnishtest

In message 4b3c5703.8020...@gmail.com, ll writes: Is there any manual about the command varnishtest ? I useing varnish 2.0.4 edition . very little. The best docs is the testcases in the tests subdirectory. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP

Architectural heads-up/call for comments

{ beresp.ttl = duration(beresp.http.myttl, 10s); } If the conversion fails because the string value is not a valid IP/time/duration, the second parameter gets used instead. Thanks for listening, now it's your turn to tell me if this is stupid... Poul-Henning -- Poul-Henning Kamp | UNIX

Re: Architectural heads-up/call for comments

In message 4b44814a.3010...@gmail.com, Rob S writes: Poul-Henning Kamp wrote: I'd like to mutter something here about adding some form of return pass, rather than just writing pass. That is already the syntax in -trunk: return(pass); 2. Client identity Access to cookies

Re: Architectural heads-up/call for comments

In message op.u55n4olks5t...@id-c0805.oslo.osa, Cosimo Streppone writes: On 06 january 2010 12:46:07, Poul-Henning Kamp p...@phk.freebsd.dk wrote: 1. Kill the magic default VCL. It's great that you're asking feedback, thanks. You will no longer be able to just give Varnish a subset

Re: Persistent mode statistics

are instantiated from the silo. Resident will increase as it gets paged in. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained

Re: logging statements in vcl

entries for every branch taken in your VCL. The number 1 case of not caching is cookies. Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately

Re: VCL config file for specific URLs

. Of course, you can also mix the two methods... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: AW: Varnish poisoned cache avoidance

to do ? Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: Varnish logging and data merging

application. run varnishncsa or varnishlog to collect your loginfo. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: AW: Varnish poisoned cache avoidance

In message 4c3149fb1001100307s4364a201n9164abbe10957...@mail.gmail.com, pub c rawler writes: Is the delay 100ms something that could be made available in Varnish near term? You can do it with inline C code already, just call usleep(10) in your inline C. -- Poul-Henning Kamp | UNIX

Re: Bug? Related to ticket 547

... ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute

Re: Does a Varnish restart clear the existing cache?

In message b6b8b6b71001141306g4dbf4292qad39e2abb86e...@mail.gmail.com, John N orman writes: I think the answer is no, but . . . Does a Varnish restart clear the existing cache? (using the file storage.) Actually it does, we are working on the persistent storage module. -- Poul-Henning

Re: Strange different behavior

: The best thing, is to not Vary on User-Agent in the first place, that's how the InterNet is supposed to work. Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute

Re: Strange different behavior

In message b6b8b6b71001150646w7f3ba876y30401d85f1813...@mail.gmail.com, John Norman writes: OK. But if your application backend really doesn't do anything different for different user agents, then one should probably remove the user-agent? yes, by all means do so. -- Poul-Henning Kamp

Re: tool for dumping contents of cache

with varnishlog and varnishtop. If you havn't yet, try: varnishtop -i rxurl -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained

Re: Strategies for splitting load across varnish instances? And avoiding single-point-of-failure?

only, the working scenario is two squids each behind a very slow line to the internet, asking each other before they pull down a file. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never

Re: Strategies for splitting load across varnish instances? And avoiding single-point-of-failure?

; } { .backend webserver; .weight 1; } } -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: Strategies for splitting load across varnish instances? And avoiding single-point-of-failure?

In message 4c3149fb1001160738l2233481dn82c34c2ba1fcc...@mail.gmail.com, pub c rawler writes: Poul, is anyone running the hash director distribution method like you provided (in production)? No idea... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP

Re: Strategies for splitting load across varnish instances? And avoiding single-point-of-failure?

In message d002c4031001160741q63dd5a50i6342116daba15...@mail.gmail.com, Micha el Fischer writes: On Sat, Jan 16, 2010 at 1:59 AM, Poul-Henning Kamp p...@phk.freebsd.dkwrote: director h1 hash { { .backend webserver; .weight 1; } { .backend varnish2; .weight

Re: Strategies for splitting load across varnish instances? And avoiding single-point-of-failure?

perfect 1/3 splitting between 3 varnishes, having one die will do bad things to your hitrate until the remaining two distribute the load between them. That's a matter of math, and has nothing to do with the hash algorithm. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org

Re: Strategies for splitting load across varnish instances? And avoiding single-point-of-failure?

traffic for its objects will be sent to it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: Strategies for splitting load across varnish instances? And avoiding single-point-of-failure?

restarts, to ask the neighbors and if they don't have it, go directly to the backend on restart. Poul-Henning [1] In general Varnish has no built in magic, all the magic is your responsibility to write in the VCL code :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org

Re: Strategies for splitting load across varnish instances? And avoiding single-point-of-failure?

varnishadm vcl.load real_thing /usr/local/etc/varnish/real.vcl varnishadm vcl.use real_thing -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can

Re: Strategies for splitting load across varnish instances? Andavoiding single-point-of-failure?

to consistent hashing and it's use... Correct me if I am wrong, but doesn't this mean that adding a new varnish instance implies a full rehash ? Yes, that is pretty much guaranteed to be the cost with any stateless hashing. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p

Re: Strategies for splitting load across varnish instances? And avoiding single-point-of-failure?

. Varnish has a significant responsibility, not yet fully met, to tell the VM system as much about what is going on as possible. Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never

Re: Varnish use for purely binary files

-20 microseconds. Compared to the amount of work real webservers do for the same task, that is essentially nothing. I don't know if that is THE best performance, but I know of a lot of software doing a lot worse. Try running varnishhist if you have not already :-) Poul-Henning -- Poul-Henning

Re: Varnish use for purely binary files

afterwards is for you to decide, but it is unlikely to be applicable. Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained

Re: Varnish use for purely binary files

few, if any, of them are. Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence

Re: Varnish use for purely binary files

translated to plain english becomes: If you don't need varnish, you don't need varnish. I'm not sure how much useful information that statement contains :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD

<    1   2   3   4   >