Re: onbar's CPU usage
vijay wrote:
>
> briceavila@hotmail.com (Brice Avila) wrote in message news:<c46e3ec5.0305290549.5ca56c32@posting.google.com>...
> > Richard Kofler <richard.kofler@chello.at> wrote in message news:<3ED537A5.8CC5439A@chello.at>...
> > > vijay wrote:
> > > >
> > > > My 9.3 IDS instance runs on an IBM RS6000 server( 4-way SP winterhawk
> > > > node 450 MHz running AIX). Everytime an onbar logical log backup kicks
> > > > off, I have noticed that it takes 25% of CPU resources(1 CPU).
> > > > Can somebody explain why the logical log backup process is so resource
> > > > intensive(all it should be doing is moving records from the logical
> > > > log on disk to the tape sub-system)?
> > > > Thanks
> > > >
> > > > -- Vijay Venkatesh
> > >
> > > are you using TIVOLI TSM?
> > >
> > > This might explain it ......
> > >
> > > And no, that is not sarkasm.
> > >
> > > If not so, then start top and find out if it is the onbar
> > > process or a CPUvp or whatever consumes all cyc1es of 1 of your CPUs
> > >
> > > dic_k
> >
> > I've used Legato and Veritas, and haven't noticed the CPU usage you've
> > seen with onbar. I haven't used Legato for a few years, but I don't
> > remember behavior like this. My Veritas NetBackup 4.5 backups barely
> > register a blip in onbar CPU usage. Hope this helps.
> >
> > Brice Avila
> > Minneapolis, Minnesota
>
> Yes, I am using TSM(4.1). I am reasonably confident that it is the
> onbar process that consumes a CPU, from the CPU time it consumes on a
> ps aux. Top should more or less return the same.
> Is there a reason you thought that onbar with TSM would do this and
> not onbar with say Legato like Brice is using? Thanks.
TSM client using the API interface has been a real CPU hog always.
On Linux/Intel and Solaris as well, YMMV, though. That is why I
suggested
to go into detail and to find out cpu usage (user and sys and wio).
TSM clients have a lot what you can configure, like buffer sizes and
window size, TCP stack parameters and so forth: It is worth to
read the manuals.
dic_k