You didn't mention the OS.

Have you considered running any diagnostic tools to figure out exactly what
process is causing the extra spikes?  For example, top or collectl (unix),
or perfmon or resource monitor (windows)?

Mike

On Wed, May 3, 2017 at 7:08 AM, Loon, Eric van (ITOPT3) - KLM <
Eric-van.Loon AT klm DOT com> wrote:

> By the way, it's not a monitoring tool because the spikes disappear right
> after the backup window...
> Kind regards,
> Eric van Loon
> Air France/KLM Storage Engineering
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Stefan Folkerts
> Sent: woensdag 3 mei 2017 10:58
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: TSM 7.1.7 server CPU behavior
>
> Hi Eric,
>
> I only have sar data of last night but I see a load around 40% that breaks
> down to 15% user, 5% system 10-20% iowait and the rest being idle.
> 10% is very low, it must be overpowered or still running a very low load.
>
> Maybe it's a monitoring tool that is hitting the system every 5 minutes,
> do you see entries in the activity log that match the load? do you seen
> more iop/s on the database?
>
>
>
>
> On Wed, May 3, 2017 at 10:30 AM, Loon, Eric van (ITOPT3) - KLM <
> Eric-van.Loon AT klm DOT com> wrote:
>
> > Hi all!
> > We are running a 7.1.7 server with a directory container storagepool
> > (dedup and compression enabled). When we have multiple clients (with
> > client-dedup disabled) backing up to it, we notice a peculiar CPU usage.
> > Overall CPU is about 10%, but we see short peaks to approx. 30% every
> > 5 minutes. Since this server is the only one with container storage
> > pools in our company I cannot compare this behavior to other TSM
> > servers. Is this behavior seen on other servers too?
> > Thanks for any help in advance!
> > Kind regards,
> > Eric van Loon
> > Air France/KLM Storage Engineering
> > ********************************************************
> > For information, services and offers, please visit our web site:
> > http://www.klm.com. This e-mail and any attachment may contain
> > confidential and privileged material intended for the addressee only.
> > If you are not the addressee, you are notified that no part of the
> > e-mail or any attachment may be disclosed, copied or distributed, and
> > that any other action related to this e-mail or attachment is strictly
> > prohibited, and may be unlawful. If you have received this e-mail by
> > error, please notify the sender immediately by return e-mail, and delete
> this message.
> >
> > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or
> > its employees shall not be liable for the incorrect or incomplete
> > transmission of this e-mail or any attachments, nor responsible for any
> delay in receipt.
> > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
> > Dutch
> > Airlines) is registered in Amstelveen, The Netherlands, with
> > registered number 33014286
> > ********************************************************
> >
> ********************************************************
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential and privileged material intended for the addressee only. If
> you are not the addressee, you are notified that no part of the e-mail or
> any attachment may be disclosed, copied or distributed, and that any other
> action related to this e-mail or attachment is strictly prohibited, and may
> be unlawful. If you have received this e-mail by error, please notify the
> sender immediately by return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
> employees shall not be liable for the incorrect or incomplete transmission
> of this e-mail or any attachments, nor responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with registered
> number 33014286
> ********************************************************
>