Re: 2.1 plans
]] Ingvar Hagelund | * Tollef Fog Heen | > a short while before Christmas, I wrote up a small document pointing to | > what I would like to get into 2.1 (...) | > Varnish 2.1 release plan | > (...) | | Will 2.1 be backwards compatible with vcl and configuration settings | from 2.0? | | ie, will I be able to just upgrade a binary pre-built package and | restart the server? Yes, I don't see any need to break backwards compatibility for 2.1. -- Tollef Fog Heen Redpill Linpro -- Changing the game! t: +47 21 54 41 73 ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: flushing cache doesn't seem to make varnish know about less
Timothy Ball wrote: > a programming error caused varnish to think there were billions of > pages it had to know about. bug is quashed but varnish doesn't seem to > know > (..) > > i tried doing url.purge ".*" and url.purge "." to no avail. "url.purge .*" will only invalidate the pages. They are not actually evicted from cache. HTTP PURGE or TTL timeout are the only ways to actually drop a page from cache, except restarting of course. > how do i make this thing forget? I guess the easiest would be a restart. -- Per Buer - Leder Infrastruktur og Drift - Redpill Linpro Telefon: 21 54 41 21 - Mobil: 958 39 117 http://linpro.no/ | http://redpill.se/ signature.asc Description: OpenPGP digital signature ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: flushing cache doesn't seem to make varnish know about less
]] Timothy Ball | a programming error caused varnish to think there were billions of | pages it had to know about. bug is quashed but varnish doesn't seem to | know | | # this is a line from top | 3596 0.2 28.3g 28g 3808 256 57m 1916 120 S 20 00 varnishd | # this is a line from ps auxwww | nobody3596 0.1 0.1 29681936 3968 ? Sl 04:24 0:00 | /opt/varnish/sbin/varnishd -a 10.13.37.1:80 -h classic -f | /etc/varnish/default.vcl -T 127.0.0.1:6082 -t 120 -w 1,500,20 | | i tried doing url.purge ".*" and url.purge "." to no avail. url.purge does not actively go out and remove the objects; they'll be picked up by the LRU cleaner after a while. If you need to recover the memory, you can do a quick «stop» and then «start» in the CLI, but this will naturally nuke your complete cache, so it can't be used if you just wanted to remove some bits. -- Tollef Fog Heen Redpill Linpro -- Changing the game! t: +47 21 54 41 73 ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Dropping some mailing lists?
Agree On Fri, Jan 9, 2009 at 10:37 AM, Tollef Fog Heen wrote: > > (Please reply only to -misc so we don't end up with a zillion copies of > this all over the lists.) > > Hi, > > we currently have very many mailing lists: > > varnish-announceRelease announcements and other important news. > varnish-bugsBug reports go here. > varnish-commit Commit messages go here. > varnish-dev Discussions regarding Varnish development. > varnish-distDiscussions regarding Varnish releases and packaging > varnish-miscDiscussions on miscellaneous topics relating to Varnish > varnish-testFor testing purposes. > > At the same time, we don't have that much traffic, so having a total of > seven mailing lists seem a bit excessive. > > I suggest we get rid of -dev, -dist and -test. -announce and -misc will > be kept as discussion lists. -bugs and -commit will continue as > trac-to-email lists (i.e. not discussion lists). > > Comments? > > -- > Tollef Fog Heen > Redpill Linpro -- Changing the game! > t: +47 21 54 41 73 > ___ > varnish-misc mailing list > varnish-misc@projects.linpro.no > http://projects.linpro.no/mailman/listinfo/varnish-misc > ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Purge change...
Right now we spend CPU&RAM to keep the built hash-string around, in case we want to hit it with purge_hash later on. purge_hash was made so that you could purge content on a particular vhost without affecting other vhosts, but due to the wierd syntax, it is not very convenient for this purpose. The proposed change is to add a new purge primitive that takes a list of (header, regexp) pairs, for instance: purge Host host3 URL "\.jpg$" But once you think about it, you can do really wierd things: purge STATUS 404 purge Set-Cookie "USER=9348395" Comments welcome... 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. ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: question about configure warning
"Michael S. Fischer" writes: > What are these "non-Linux-specific issues" to which the document refers? The lack of a completion indicator + various implementation bugs. The only OS I know of that has a usable implementation is FreeBSD 8. DES -- Dag-Erling Smørgrav - d...@des.no ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Purge change...
Poul-Henning Kamp wrote: > The proposed change is to add a new purge primitive that takes a > list of (header, regexp) pairs, for instance: > > purge Host host3 URL "\.jpg$" > > But once you think about it, you can do really wierd things: > > purge STATUS 404 This looks really useful. It can be used to implement "cache channels" - don't worry, we'll do the RSS and other stuff outside of Varnish. :-) One thing bothers me, however. This will mean we will accumulate a longer and longer list or active purges. AFAIK this can be helped by two means 1) The nuke thread. One threads which walks the heap and kills of purged objects and shortens the list of purges. 2) Setting a TTL on a purge statement. If you have a maximum TTL of 24hrs there is no point in keeping the purge statement around and checking incomming URIs against it after 24hrs. 2) might even make sense today. -- http://linpro.no/ | http://redpill.se/ signature.asc Description: OpenPGP digital signature ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
