On Apr 4, 2008, at 2:04 PM, Michael S. Fischer wrote:
> On Fri, Apr 4, 2008 at 11:05 AM, Ricardo Newbery <[EMAIL PROTECTED]
> > wrote:
>
>> Again, "static" content isn't only the stuff that is served from
>> filesystems in the classic static web server scenario. There are
>> plenty of
>> "dyn
On Fri, Apr 4, 2008 at 11:05 AM, Ricardo Newbery <[EMAIL PROTECTED]> wrote:
> Again, "static" content isn't only the stuff that is served from
> filesystems in the classic static web server scenario. There are plenty of
> "dynamic" applications that process content from database -- applying skin
Sascha Ottolski wrote:
> Am Freitag 04 April 2008 18:11:23 schrieb Michael S. Fischer:
>
>> Ah, I see.
>>
>> The problem is that you're basically trying to compensate for a
>> congenital defect in your design: the network storage (I assume NFS)
>> backend. NFS read requests are not cacheable by
On Apr 4, 2008, at 2:50 AM, Michael S. Fischer wrote:
> On Thu, Apr 3, 2008 at 8:59 PM, Ricardo Newbery <[EMAIL PROTECTED]
> > wrote:
>
>> Well, first of all you're setting up a false dichotomy. Not
>> everything
>> fits neatly into your apparent definitions of dynamic versus
>> static. Yo
Am Freitag 04 April 2008 18:11:23 schrieb Michael S. Fischer:
> On Fri, Apr 4, 2008 at 3:20 AM, Sascha Ottolski <[EMAIL PROTECTED]>
wrote:
> > you are right, _if_ the working set is small. in my case, we're
> > talking 20+ mio. small images (5-50 KB each), 400+ GB in total
> > size, and it's grow
On Fri, Apr 4, 2008 at 3:20 AM, Sascha Ottolski <[EMAIL PROTECTED]> wrote:
> you are right, _if_ the working set is small. in my case, we're talking
> 20+ mio. small images (5-50 KB each), 400+ GB in total size, and it's
> growing every day. access is very random, but there still is a good
> am
Am Freitag 04 April 2008 11:50:51 schrieb Michael S. Fischer:
> On Thu, Apr 3, 2008 at 8:59 PM, Ricardo Newbery
<[EMAIL PROTECTED]> wrote:
> > Well, first of all you're setting up a false dichotomy. Not
> > everything fits neatly into your apparent definitions of dynamic
> > versus static. Your
On Thu, Apr 3, 2008 at 8:59 PM, Ricardo Newbery <[EMAIL PROTECTED]> wrote:
> Well, first of all you're setting up a false dichotomy. Not everything
> fits neatly into your apparent definitions of dynamic versus static. Your
> definitions appear to exclude the use case where you have cacheable c
Am Freitag 04 April 2008 10:11:52 schrieb Stig Sandbeck Mathisen:
> On Fri, 4 Apr 2008 09:01:57 +0200, Sascha Ottolski <[EMAIL PROTECTED]>
said:
> > I definetely did nothing like this, I've observed restarts "out of
> > the blue". I'm no giving the trunk a try, hopefully there's an
> > improvement
after checking out and running autogen.sh, configure stops with this
error:
./configure: line 19308: syntax error near unexpected token
`VARNISHAPI,'
./configure: line 19308: `PKG_CHECK_MODULES(VARNISHAPI, varnishapi)'
Cheers, Sascha
___
varnish-misc
On Fri, 4 Apr 2008 09:01:57 +0200, Sascha Ottolski <[EMAIL PROTECTED]> said:
> I definetely did nothing like this, I've observed restarts "out of
> the blue". I'm no giving the trunk a try, hopefully there's an
> improvement to that matter.
If the varnish caching process dies for some reason, the
Hi,
sorry if this is FAQ: what can I do to make varnish respond to request
if it's backend is dead. should return cache hits, of course, and
a "proxy error" or something for a miss.
and how can I prevent varnish to cache "404" for objects it couldn't
fetch due to a dead backend? at least I thi
Am Freitag 04 April 2008 04:37:44 schrieb Ricardo Newbery:
> sub vcl_fetch {
> if (obj.ttl < 120s) {
> set obj.ttl = 120s;
> }
> }
>
> Or you can invent your own header... let's call it X-Varnish-1day
>
> sub vcl_fetch {
>
Am Freitag 04 April 2008 01:32:28 schrieb DHF:
> Sascha Ottolski wrote:
> > however, my main problem is currently that the varnish childs keep
> > restarting, and that this empties the cache, which effectively
> > renders the whole setup useless for me :-( if the cache has filled
> > up, it works g
14 matches
Mail list logo
