[Top] [All Lists]

Re: [pcp] Culling code from libpcp

To: Greg Banks <gnb@xxxxxxxxxxx>
Subject: Re: [pcp] Culling code from libpcp
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu, 6 May 2010 16:36:57 +1000 (EST)
Cc: pcp@xxxxxxxxxxx
In-reply-to: <4BE25C8F.2050307@xxxxxxxxxxx>
----- "Greg Banks" <gnb@xxxxxxxxxxx> wrote:
> Well...I don't think you'd need locking and threading everywhere.  You

By "everywhere" I mean on every (runtime) code path.  pdubuf.c would
need locking or rewriting or thread-localising or whatever - everything
goes through there, including pmcd and pmdas.

> You are lucky.  I use it daily with hosts located two rooms away and
> it  locks up for several seconds each day.

Hmm, I find that very hard to believe.  (Would you believe several
milliseconds?!?)  Is your update interval is insanely high?  Where
is the root cause of your lockups?  (why does it take that long to
talk to a machine two rooms away?)

> > then my vote would be for separate processes per-context
> communicating
> > with a common graph/UI process via mmap or something like that.
> >   
> Sigh.

Why the need for threads over processes?  (when pmcd/pmda end is already
using processes for this class of issue ... so why threads on the client



<Prev in Thread] Current Thread [Next in Thread>