Hi. I've just subscribed, and have been reading through the e-mail archives
for varnish-misc.
In Dec. 2009, Jean-Christophe Petit asked (with subject still using cache
when fetching content):
-
Is it possible to make Varnish sending the cache content at the same
time it is fetching from the
I think Chris Davies has straightened me out, and that the scenario I
describe *is* covered by grace -- that the first hit would also get stale
(as well as others in the grace period), which is exactly what I want.
On Fri, Jan 8, 2010 at 4:20 PM, John Norman j...@7fff.com wrote:
Hi. I've just
On Thu, Jul 09, 2009 at 02:17:35PM -0500, Brian Pan wrote:
Hi all,
I have a newbie question regarding 'purging the cache.' When I run the
following command to purge the root domain of my website,
varnishadm -T localhost:80 purge.url ^/$
Are you sure the admin interface is at port 80
Hi all,
I have a newbie question regarding 'purging the cache.' When I run the
following command to purge the root domain of my website,
varnishadm -T localhost:80 purge.url ^/$
I get this error:
An error occured in receiving status.
Based on examples, I've setup my VCL as follows
]] Poul-Henning Kamp
| In message 5c056ae2-7207-42f8-9e4b-0f541dc4b...@slide.com, Ken Brownfield
wri
| tes:
|
| Would a stack overflow take out the whole child, or just that thread?
|
| The kernel would try to extend the stack and provided you are not on
| a 32 bit system, it shouldn't ever
Overcommit defaults off; sane use cases for overcommit are few and far
between, IMHO. With overcommit on, the performance implications might
be more of a wash... but then you have two problems.
Even though the stack remains mostly unused, it would still have to be
swapped out under memory
When looking at /proc/map info for varnish threads, I'm seeing the
following allocations in numbers that essentially match the child count:
40111000 8192K rw---[ anon ]
And this at almost double the child count:
7f4d5790 1024K rw---[ anon ]
For example, for 64
]] Ken Brownfield
| When looking at /proc/map info for varnish threads, I'm seeing the
| following allocations in numbers that essentially match the child count:
|
| 40111000 8192K rw---[ anon ]
Looks like the default stack size.
| And this at almost double the child count:
|
On Jun 19, 2009, at 7:15 AM, Tollef Fog Heen wrote:
| 40111000 8192K rw---[ anon ]
Looks like the default stack size.
Ah, of course. Good find, thanks. I'm thinking it might be nice to
have a thread track its stack history and emit its approximate largest
size when it's
In message 5c056ae2-7207-42f8-9e4b-0f541dc4b...@slide.com, Ken Brownfield wri
tes:
Would a stack overflow take out the whole child, or just that thread?
The kernel would try to extend the stack and provided you are not on
a 32 bit system, it shouldn't ever have a problem with that.
--
]] Monah Baki
| Here is part of the logs, how can I tell it's working?
It doesn't seem to be caching, most likely because the backend sets a
cookie (which means we, by default, don't cache).
--
Tollef Fog Heen
Redpill Linpro -- Changing the game!
t: +47 21 54 41 73
Hi,
Can anyone explain to me those varnishlog entries mean ?
0 ExpPick - 1369849794 ttl
0 VCL_call - timeout
0 VCL_return - discard
0 ExpKill - 1369849794 -10
They always come in this order.
Thanks J
Shahar Fleischman sha...@mindu.co.il writes:
Can anyone explain to me those varnishlog entries mean ?
0 ExpPick - 1369849794 ttl
0 VCL_call - timeout
0 VCL_return - discard
0 ExpKill - 1369849794 -10
Object 1369849794 was selected as a candidate for expiry on
Hi all,
Up to now, i'm been running standalone varnish on 2 servers (for
redundoncy).
I've been asked to have those 2 varnish work together :
if there is miss on server1, server1 asks server2 (in case server2 has
the object in cache), before asking the backend
Do any of you have any
Tollef Fog Heen a écrit :
]] Damien Desmarets
| I have 1 question for you. I haven't found the response in the
| documentation/wiki. I think you have a big job to wrtie a good
| documentation ... the current is really poor !
If you want to help out with writing docs or suggest weak points
]] Damien Desmarets
| I have 1 question for you. I haven't found the response in the
| documentation/wiki. I think you have a big job to wrtie a good
| documentation ... the current is really poor !
If you want to help out with writing docs or suggest weak points, you
are more than welcome
Hello,
I have 1 question for you. I haven't found the response in the
documentation/wiki. I think you have a big job to wrtie a good
documentation ... the current is really poor !
So the question.
I have a list of differents domains:
azeazeaze.com
eruigeiogr.com
zezeirjiorf.com
...
My
Michael S. Fischer mich...@dynamine.net 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 -
Hi all
I'm setting up an amd64 box (that is intel xeon x86_64) with ubuntu
8.04 and varnish 2.0.2, and configure gives me a warning about sendfile
configure: WARNING: won't look for sendfile() on x86_64-unknown-
linux-gnu
Does this mean it won't be using sendfile() on this system?
roy
--
Roy Sigurd Karlsbakk wrote:
Does this mean it won't be using sendfile() on this system?
If I recall correctly, it won't be using sendfile() on *almost all*
systems (except certain versions of BSD?). From the porting pages:
The build system will automatically detect the availability of epoll()
On Jan 6, 2009, at 7:42 AM, Marcus Smith wrote:
The build system will automatically detect the availability of
epoll()
and build the corresponding cache_acceptor. It will also automatically
detect the availability of sendfile(), though its use is discouraged
(and disabled by default) due to
Hi,
I've been playing with Varnish for a couple of months now: impressive, really !
I would like to replay Apache logs.
Is there a way to run varnishreplay -r ncsa-file ?
If no, could that be consider as a future enhancement ?
Thx by advance,
Serge
Hi all,
I configured the Varnish 1.1.2-r2635 to allow purging from backoffice
web servers. The first version of this concept is very easy, just send
PURGE request for specific URL to Varnish servers.
Configuraiton,
VCL_RECV
if (req.request == PURGE) {
if (client.ip ~
Im running 32bit. But I think that I have succeded creating more then
238 threads before on another system with the same setup.
Anyway, 64bit might be the thing to have...
If I want to have Debian, is it AMD64 version that I should go for? (OT)
/ E
Poul-Henning Kamp skrev:
In message [EMAIL
In message [EMAIL PROTECTED], Erik Torlen writes:
Im running 32bit. But I think that I have succeded creating more then
238 threads before on another system with the same setup.
Anyway, 64bit might be the thing to have...
If I want to have Debian, is it AMD64 version that I should go for? (OT)
Erik Torlen skrev:
Im running 32bit. But I think that I have succeded creating more then
238 threads before on another system with the same setup.
Anyway, 64bit might be the thing to have...
Maybe the init script should issue a warning that a 32bit arch is only
usable as a test enviroment.
In message [EMAIL PROTECTED], Per Buer writes:
Maybe the init script should issue a warning that a 32bit arch is only
usable as a test enviroment.
Well, Varnish is generally usable in 32bit, provided you have
very small content, so I'm hessitant to rule it entirely out,
but yes, we clearly need
Thanks for the tips, I will test this and come back with the result.
/ E
Original Message ---
On Wed, 18 Jun 2008 13:24:52 -0700
Michael S. Fischer [EMAIL PROTECTED] wrote:
On Wed, Jun 18, 2008 at 4:51 AM, Rafael Umann
[EMAIL PROTECTED] wrote:
If it is a 32bits
In message [EMAIL PROTECTED], [EMAIL PROTECTED] writes:
1. The 32bits arch (cant open threads and the storage file is too
small), so im moving into 64bits.
Yes, 32bit is generally not big enough to Varnish for non-trivial
workloads.
2. The cpu usage of the listener process with 2 hits/sec
* Oliver Oli
| are there any debian buildpackage scripts available?
Yes, you get them in the debian/ directory if you do a subversion
checkout.
--
Tollef Fog Heen / Linpro ASt: 21 54 41 73
UNIX is user friendly, it's just picky about who its friends are
how about your storage file size?
[]s,
On Mon, 23 Jun 2008 21:20:59 +0200
Erik Torlen [EMAIL PROTECTED] wrote:
I still have the same problem :(
The threads are created up to 238 where they are stopped, even if I
set threads_max = 1000 and threads_pools = 2 (or 3).
I also tested the tips
In message [EMAIL PROTECTED], Erik Torlen writes:
I still have the same problem :(
The threads are created up to 238 where they are stopped, even if I set
threads_max = 1000 and threads_pools = 2 (or 3).
I also tested the tips and decreased the stack sixe to 512 and increased
overflow_max to
are there any debian buildpackage scripts available?
On Sat, Jun 21, 2008 at 11:59 AM, Poul-Henning Kamp [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Damien Sarazin writes:
My question is : should i continue to work with the 1.1.2 release or is
the 1.2 version stable enough so i can
In message [EMAIL PROTECTED], Damien Sarazin writes:
My question is : should i continue to work with the 1.1.2 release or is
the 1.2 version stable enough so i can use this last one ?
Actually, we are heading into the 2.0 release cycle, so you should
grab a -trunk copy from SVN and look
On Wed, 18 Jun 2008 13:24:52 -0700
Michael S. Fischer [EMAIL PROTECTED] wrote:
On Wed, Jun 18, 2008 at 4:51 AM, Rafael Umann
[EMAIL PROTECTED] wrote:
If it is a 32bits system, probably the problem is that your stack
size is 10Mb. So 238 * 10mb = ~2gb
I decreased my stack size to
On Thu, Jun 19, 2008 at 5:37 AM, Rafael Umann [EMAIL PROTECTED]
wrote:
What is your request:connection ratio?
Unfortunately now i dont have servers doing 2 hits/second, and
thats why i dont have stats for you.
Actually, it's right there in your varnishstat output:
36189916
On Thu, 19 Jun 2008 08:05:21 -0700
Michael S. Fischer [EMAIL PROTECTED] wrote:
On Thu, Jun 19, 2008 at 5:37 AM, Rafael Umann
[EMAIL PROTECTED] wrote:
What is your request:connection ratio?
Unfortunately now i dont have servers doing 2 hits/second, and
thats why i dont have stats
On Wed, Jun 18, 2008 at 4:51 AM, Rafael Umann [EMAIL PROTECTED]
wrote:
If it is a 32bits system, probably the problem is that your stack size
is 10Mb. So 238 * 10mb = ~2gb
I decreased my stack size to 512Kb. Using 1gb storage files i can now
open almost 1900 threads using all the 2gb that
I recently made a loadtest against through varnish.
First I received a very high response time and found out that varnish was
maxing the maximum nr of threads.
I updated thread_min = 5 and thread_max = 300 and recevied much better resp.
times.
Then I increased the nr of concurrent users and
Raising the number of threads will not significantly improve Varnish
concurrency in most cases. I did a test a few months ago using 4 CPUs on
RHEL 4.6 with very high request concurrency and a very low
request-per-connection ratio (i.e., 1:1, no keepalives) and found that the
magic number is about
In message [EMAIL PROTECTED], David Pratt writes:
Hi. Sorry for not getting back sooner. The use case I have is have
backend determine when frequency reaches a threshold and set ttl
dynamically based on the rate. [...]
And Varnish is a perfect frontend for that.
--
Poul-Henning Kamp |
writes:
Hi. In most cases, I want a request to be passed to a backend where it
will be handled by server. If frequency is high, however; I want to add
the object to varnish cache and have varnish handle it. I am not worried
about a mechanism to keeping track of frequency of requests. Question
In message [EMAIL PROTECTED], Barry Abraham
son writes:
On Jun 2, 2008, at 8:41 AM, Poul-Henning Kamp wrote:
We do this on WordPress.com to avoid filling our caches with
infrequently requested data. The way we handle it is when an object
reaches a certain req/sec threshold, we send a header
to add
the object to varnish cache and have varnish handle it. I am not worried
about a mechanism to keeping track of frequency of requests. Question is
what is available to me to add an object/path to the varnish cache if it
was originally passed? Many thanks.
Regards,
David
Hi. In most cases, I want a request to be passed to a backend where it
will be handled by server. If frequency is high, however; I want to add
the object to varnish cache and have varnish handle it. I am not worried
about a mechanism to keeping track of frequency of requests. Question is
what
james wrote:
Hey everyone,
In trying to diagnose why the varnish child dies at seemingly random
times, I started varnish with -d -d and waited for a crash. This is what
I got in the output:
Child said (2, 16094): Assert error in STV_alloc(), stevedore.c line 70:
Condition((st) != NULL)
Hey everyone,
In trying to diagnose why the varnish child dies at seemingly random
times, I started varnish with -d -d and waited for a crash. This is what
I got in the output:
Child said (2, 16094): Assert error in STV_alloc(), stevedore.c line 70:
Condition((st) != NULL) not true.
errno
James Quacinella [EMAIL PROTECTED] writes:
From the man page: vcl_pass: Called upon entering pass mode. In this
mode, the request is passed on to the backend, and the backend's
response is passed on to the client, but is not entered into the
cache. Subsequent requests submitted over the same
48 matches
Mail list logo