[p4] P4 monitor show
Jamie.Echlin@barclayscapital.com
Jamie.Echlin at barclayscapital.com
Mon Jan 8 02:06:03 PST 2007
many thanks for the suggestion Guillaume, it sounds pretty good.
Could I also ask a slightly simpler question - does anyone know if it's
still necessary to create a separate perforce instance with the monitor
db table linked in, because "p4 monitor" stops working under heavy load?
As mentioned the google presentation implied that this would be fixed
shortly.
cheers, jamie
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of G Barthelemy
> Sent: 05 January 2007 23:40
> To: Echlin, Jamie: IT (LDN)
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] P4 monitor show
>
>
> On 1/5/07, Jamie.Echlin at barclayscapital.com
> <Jamie.Echlin at barclayscapital.com> wrote:
> > I appreciate that, but it doesn't get round the fact that
> the monitor
> > command can fail to run wherever it is run, even if it's
> only run once
> > every 3 seconds even if a hundred people are viewing the page.
>
> Could an alternative approach be to parse p4d's error log on the
> server, assuming you have debug set to at least "server=2" which would
> give you the completion time for each command?
>
> Sure it would be more involved than monitoring the output of "monitor
> show" as you would need to remember what command has been started when
> (and from time to time check that the PID is still in the process
> table as commands can be aborted without a completion being logged),
> but all in all this could be a way of monitoring your Perforce server
> activity in real time, without having to resort to run p4 commands,
> making for a less intrusive or expensive method.
>
> If your log was written to a volume that's mounted from another
> machine, or rsync'd to another machine, you could even process it away
> from your production server, and therefore with very little CPU cost.
>
> --
> Guillaume Barthelemy
> _______________________________________________
> perforce-user mailing list - perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
------------------------------------------------------------------------
For more information about Barclays Capital, please visit our web site at http://www.barcap.com.
Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email may be monitored by the Barclays Group for operational or business reasons.
------------------------------------------------------------------------
More information about the perforce-user
mailing list