On Thu, Dec 10, 2009 at 8:50 AM, Bernd Walter wrote:
> On Wed, Dec 09, 2009 at 09:07:33AM -0500, John Baldwin wrote:
> > On Thursday 26 November 2009 10:14:20 am Linda Messerschmidt wrote:
> > > It's not clear to me if this might be a problem with the superpages
> > > implementation, or if squid d
On Thu, 10 Dec 2009, Nate Eldredge wrote:
What about using posix_spawn(3)? This is implemented in terms of vfork(),
so you'll gain the same performance advantages, but it avoids many of
vfork's pitfalls. Also, since it's a POSIX standard function, you needn't
worry that it will go away or c
On Thursday 10 December 2009 9:50:52 am Bernd Walter wrote:
> On Wed, Dec 09, 2009 at 09:07:33AM -0500, John Baldwin wrote:
> > On Thursday 26 November 2009 10:14:20 am Linda Messerschmidt wrote:
> > > It's not clear to me if this might be a problem with the superpages
> > > implementation, or if s
Depending upon the IPC method being used, the fork() may be followed
with calls to socket() and connect(), which may take a while.
The main process will stall if you have a busy proxy and there's some
temporary shortage of something which makes connect() take longer than
usual, the main process wi
On Mon, Dec 07, 2009 at 04:20:03PM +0100, Mel Flynn wrote:
> On Thursday 26 November 2009 18:11:10 Linda Messerschmidt wrote:
>
> > I did not mean to suggest that we were asking for help solving a
> > problem with squid rotation. I provided that information as
> > background to discuss what we ob
On Thu, 10 Dec 2009, Linda Messerschmidt wrote:
Also...
On Thu, Dec 10, 2009 at 9:50 AM, Bernd Walter wrote:
I use fork myself, because it is easier sometimes, but people writing
big programms such as squid should know better.
If squid doesn't use vfork they likely have a reason.
Actually t
Also...
On Thu, Dec 10, 2009 at 9:50 AM, Bernd Walter wrote:
> I use fork myself, because it is easier sometimes, but people writing
> big programms such as squid should know better.
> If squid doesn't use vfork they likely have a reason.
Actually they are probably going to switch to vfork(). T
On Thu, Dec 10, 2009 at 9:50 AM, Bernd Walter wrote:
> I obviously don't have enough clue about this to understand those details.
> Hope that someone can enlighten me.
I think what he is saying is that they are aware that the current
situation is not ideal.
vfork() is suggested as a workaround,
On Wed, Dec 09, 2009 at 09:07:33AM -0500, John Baldwin wrote:
> On Thursday 26 November 2009 10:14:20 am Linda Messerschmidt wrote:
> > It's not clear to me if this might be a problem with the superpages
> > implementation, or if squid does something particularly horrible to
> > its memory when it
On Wed, Dec 9, 2009 at 9:07 AM, John Baldwin wrote:
> There is lower hanging fruit in other areas
> in the VM that will probably be worked on first.
OK, as long as somebody who knows more than me knows whats going on,
that's good enough for me. :)
Thanks!
On Thursday 26 November 2009 10:14:20 am Linda Messerschmidt wrote:
> It's not clear to me if this might be a problem with the superpages
> implementation, or if squid does something particularly horrible to
> its memory when it forks to cause this, but I wanted to ask about it
> on the list in cas
on 07/12/2009 17:20 Mel Flynn said the following:
> b) vfork is encouraged for memory intensive applications, yet:
> BUGS
> This system call will be eliminated when proper system sharing mechanisms
> are implemented. Users should not depend on the memory sharing semantics
> of vfork
On Thursday 26 November 2009 18:11:10 Linda Messerschmidt wrote:
> I did not mean to suggest that we were asking for help solving a
> problem with squid rotation. I provided that information as
> background to discuss what we observed as a potential misbehavior in
> the new VM superpages feature,
On Fri, 27 Nov 2009, Adrian Chadd wrote:
> There's a bunch of other random crap that may be going on relating to
> the helper processes (eg rewriters, auth, etc) which may also be
> restarted.
OK.
> Anyway. The thread is about superpage demotion and copying, not what
> Squid is or isn't doing in
There's a bunch of other random crap that may be going on relating to
the helper processes (eg rewriters, auth, etc) which may also be
restarted.
Anyway. The thread is about superpage demotion and copying, not what
Squid is or isn't doing in her configuration. :)
Adrian
2009/11/27 Daniel O'Con
On Fri, 27 Nov 2009, krad wrote:
> Im sure you will get a lot of lovely answers to this but best keep
> things simple. WHy not just syslog it of to another server and
> offload all the compression to that box. You could even back it with
> zfs nad do on the fly gzip compression at the file system l
2009/11/26 Linda Messerschmidt
> We have a squid proxy process with very large memory requirements (10
> - 20 GB) on a machine with 24GB of RAM.
>
> Unfortunately, we have to rotate the logs of this process once per
> day. When we do, it fork()s and exec()s about 16-20 child processes
> as helpe
I think I was not clear with my message, I apologize.
I did not mean to suggest that we were asking for help solving a
problem with squid rotation. I provided that information as
background to discuss what we observed as a potential misbehavior in
the new VM superpages feature, in the hope that i
Hi Linda,
vfork() should mitigate this -- i suggest replacing.
respectfully,
=jt
On Thu, Nov 26, 2009 at 10:47, Linda Messerschmidt
wrote:
> On Thu, Nov 26, 2009 at 10:34 AM, Ryan Stone wrote:
>> Is squid multithreaded?
>
> No, it isn't:
>
> PID USERNAME THR PRI NICE SIZE RES STATE C
Dag-Erling Smørgrav writes:
> Linda Messerschmidt writes:
> > Unfortunately, we have to rotate the logs of this process once per
> > day. When we do, it fork()s and exec()s about 16-20 child processes
> > as helpers.
> s/fork/vfork/ and you should be fine.
...and you should look into replacing
Linda Messerschmidt writes:
> Unfortunately, we have to rotate the logs of this process once per
> day. When we do, it fork()s and exec()s about 16-20 child processes
> as helpers.
s/fork/vfork/ and you should be fine.
DES
--
Dag-Erling Smørgrav - d...@des.no
__
On Thu, Nov 26, 2009 at 10:34 AM, Ryan Stone wrote:
> Is squid multithreaded?
No, it isn't:
PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND
75086 squid 1 40 12571M 12584M kqread 6 31:31 0.68% squid
Thanks!
___
Is squid multithreaded? My first guess would be that you have one
thread forking off all of these processes while other threads are
still doing work and writing to different parts of the address space.
I don't know the details of the superpages implementation but I could
definitely see that this c
We have a squid proxy process with very large memory requirements (10
- 20 GB) on a machine with 24GB of RAM.
Unfortunately, we have to rotate the logs of this process once per
day. When we do, it fork()s and exec()s about 16-20 child processes
as helpers. Since it's got this multi-million-entry
24 matches
Mail list logo
