Re: Number of cached objects

In message c98122ba1003091910y6de964beue598f69b406a9...@mail.gmail.com, Brad Schick writes: Its not clear to which field is the number of cache entries. Perhaps shm_records? You want n_object -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC

Re: locking SHMFILE in core failed: Cannot allocate memory

allocate memory Don't worry about it, it's just noise. -- 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 CLI user feedback, please.

on the CLI interface ? -- 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: health check path doesn't change after VCL reload (2.0.6)

In message b6b8b6b71002241315w1c62022t1bf941d6f2cac...@mail.gmail.com, John N orman writes: Still, the VCL indicated as active had a different path for the health check. Hopefully both got probed ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since

Re: Child panics on OpenSolaris

In message 4b7bc0d5.7080...@schokola.de, Nils Goroll writes: That's another piece of autocrap stuff that needs fixed... Do you want me to do it? Send patches! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD

Re: Child panics on OpenSolaris

In message 282e72051002170310g565a26d8s98170fcebb9b2...@mail.gmail.com, Paul Wright writes: On 17 February 2010 10:57, Poul-Henning Kamp p...@phk.freebsd.dk wrote: I have pulled the latest revision and can confirm that unlink(/) failed as expected. I ran it briefly and saw this panic: Child

Re: Child panics on OpenSolaris

In message 282e72051002150322l57063a9ds98143093910c2...@mail.gmail.com, Paul Wright writes: On 13 February 2010 20:26, Poul-Henning Kamp p...@phk.freebsd.dk wrote: I'm still not 100% convinced that EBADF is not me screwing something up, so I have gone over the poll-waiter and made it even more

Re: Child panics on OpenSolaris

... -- 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 mailing list

Re: Child panics on OpenSolaris

In message 89581.1265999...@critter.freebsd.dk, Poul-Henning Kamp writes: In message 282e72051002120949u56eb6914mbd55e5a355931...@mail.gmail.com, Paul Here's a snippet from varnishlog for one of these panics (also attached to this email in case line wraps wreck formatting): Interesting

Aiming for Varnish 2.1

is cut. On the down-side: * -spersistent still not done. * Various solaris issues still not resolved. * You need to change your VCL at bit. * We still have a half hundred open tickets. * Some new bugs, didn't see them, but I know they are there. Enjoy, Poul-Henning -- Poul-Henning

Re: Child panics on OpenSolaris

varnishlog for these connections ? I wonder if Solaris has some kind of I already told you it were closed once logic... -- 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

Re: Child panics on OpenSolaris

is sent ? If so: does the client ACK the response, before the RST ? If so: how long time elapses between the ACK and the RST ? -- 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: ESI include inserts garbage code

we use to transmit ESI with to HTTP/1.1 clients... -- 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: ESI include inserts garbage code {SOLVED]

In message 4b749cb9.6080...@bugbyte.nl, Bert-Jan de Lange writes: The checksums are gone now. Well, they're not really checksums, they are byte counts, but... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD

Re: Maintenance message

req.backend = maint; } } -- 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: Error compiling VCL when using '% in regexp

is 4 ### s1 rxreq s1 rxhdr| GET /foo HTTP/1.1\r\n s1 rxhdr| X-Forwarded-For: 127.0.0.1\r\n s1 rxhdr| X-Varnish: 1001\r\n s1 rxhdr| Host: 127.0.0.1\r\n s1 rxhdr| \r\n -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP

Re: Child panics on OpenSolaris

. The alternative explanation, that Solaris can return EBADF because the other end closed a TCP connection, does not seem to have any support in Solaris documentation. We are trying to get a Solaris box running so we can figure this out once and for all. -- Poul-Henning Kamp | UNIX since Zilog

Re: Child panics on OpenSolaris

incorrectly closes the fd. 3. Setup some synthetic test to show that solaris returns EBADF when it shouldn't If either of those are in your reach, by all means go for it... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer

Re: Varnish Software

an excuse for growing up the project a bit, so I have, hopefully for the last time, used my dictatorial powers and appointed: Arther sky Bergman (users) Kristan Lyngstol (commercial) Poul-Henning Kamp (developers) to the Interrim Varnish Governing Board, which is tasked

Re: varnishlog not behaving as expected (by me)

In message 871vgwc5vk@qurzaw.linpro.no, Tollef Fog Heen writes: ]] Poul-Henning Kamp | In message 4b6960da.6080...@bmjgroup.com, Alex Hooper writes: | |/usr/local/bin/varnishlog -o RxURL ^wp-admin$ | | This says you want to *O*mit all RxURL lines. The regexp argument | should have

Re: Error compiling VCL when using '% in regexp

... -- 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 mailing

Re: obj.cacheable vs expires headers?

that says that the object can not be cached, that solves a pile-up issue on busy objects. The fact that you see zero TTL, can be indicative of the clock on the varnish-host and the clock on the backend not agreeing what time it is. Check your ntpd. -- Poul-Henning Kamp | UNIX since Zilog Zeus

Re: obj.cacheable vs expires headers?

In message 4b708469.9070...@gmail.com, Luc Stroobant writes: Poul-Henning Kamp wrote: Check your varnishlog output, it shows all headers sent/received and look for what cache-control the backend gives varnish... The cache-control headers of the backend seem to be ok? (btw, the Varnish test

Re: varnishlog not behaving as expected (by me)

: Include (only) RxURL lines, which match this regexp. -- 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: Upper and lower case strings in Varnish

been randomly capitalising them when linking to them - I'd just like Varnish to issue a 301 redirect to the lowercased version of the URL: everything is in place apart from converting the string to lowercase. You'll have to use a bit of inline C code to do that. Poul-Henning -- Poul-Henning

Re: Memory usage

larger than 4G, getting a SSD disk instead might be a better investment. 3. I noticed tonight that my machine was using a few hundred megs of swap space, Yes, varnish will force inactive programs (inetd, getty, sendmail etc) out to swap so it can get at the RAM. -- Poul-Henning Kamp | UNIX

Re: varnishhist x-axis?

In message 4b66a916.4000...@netmatch.nl, =?ISO-8859-1?Q?Angelo_H=F6ngens?= wr ites: So for my understanding (oversimplified): This is the number of seconds it takes Varnish to 'get the result', either from the backend or from it's cache? Yes. -- Poul-Henning Kamp | UNIX since Zilog Zeus

Re: Varnish Prefetch

In message 75cf5801001270025s722f114ax9335dba334a84...@mail.gmail.com, Paras Fadte writes: Thanks for the response . So with grace mode is it possible to fetch an object from backend about x seconds before its expires time is reached ? No, sorry. -- Poul-Henning Kamp | UNIX since Zilog

Re: Varnish Prefetch

In message 75cf5801001241820w3e4afd34v64ad2031b8b7...@mail.gmail.com, Paras Fadte writes: Is prefetch by default enabled in varnish ? Prefetch never got implemented, we found other ideas to solve the problem, such as grace mode. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p

Re: Compiling VCL with pcc

varnishd with -C option to capture a copy of the C program which pcc is being asked to compile. Check the line number and see what it chokes on. -- 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 crashes

a -sfile for each disk. -- 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 crashes

of load, make sure to kldload the http accept filter. Your varnish-stat looks pretty OK. Have you configured health-polling of all those backends ? -- 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 use for purely binary files

for optimization = there. You should really read the varnish_perf.pdf slides I linked to yesteday... -- 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: Feature REQ: Match header value against acl

to string, will be explicit and provide a default, so the above would become: if (!IP(req.http.X-Forwarded-For, 127.0.0.2) ~ purge) { ... If the X-F-F header is not there, or does not contain an IP#, 127.0.0.2 will be used instead. -- Poul-Henning Kamp | UNIX since

Re: Health check -- just connect, or full response?

In message b6b8b6b71001191152u7be99773o5ec70b20026...@mail.gmail.com, John No rman writes: Folks, For the health check (or, ahem, backend probe, as the docs has it -- ouch!), does health constitute ability to connect? Or does it check for a 200? It checks 200 -- Poul-Henning Kamp | UNIX

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

Re: Handling of cache-control

? Because we wanted to give the backend a chance to tell Varnish one thing with respect to caching, and the client another. I'm not saying we hit the right decision, and welcome any consistent, easily explainable policy you guys can agree on. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p

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? 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: 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: 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: 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: 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: 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: 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: 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

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: 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

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: 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: 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: 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

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: 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

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: 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

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: 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: 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: 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

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: 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

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: 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

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: 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: 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: 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: 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: 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

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: 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

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: 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

  1   2   3   4   >