<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: diagmond performance hit every 290 secs in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/diagmond-performance-hit-every-290-secs/m-p/5231491#M468528</link>
    <description>stm is current spec for 11.11. hardware is 5470's 34440's&amp;amp; 4440's. Is we stop diagmond - no performace hiccups. we have them at 290 secs 5 mins &amp;amp; 10 min intervals</description>
    <pubDate>Mon, 22 Mar 2010 20:18:41 GMT</pubDate>
    <dc:creator>Terry L Johnson</dc:creator>
    <dc:date>2010-03-22T20:18:41Z</dc:date>
    <item>
      <title>diagmond performance hit every 290 secs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diagmond-performance-hit-every-290-secs/m-p/5231488#M468525</link>
      <description>nothing is set at this interval, but a major perf hit every 290 secs. default ioscan is turned to off. 1 what is responsible for this &amp;amp; 2 what are the ramifications if I turn diagnostics off? PS this will affect about 3000 systems worldwide.....</description>
      <pubDate>Mon, 22 Mar 2010 15:04:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diagmond-performance-hit-every-290-secs/m-p/5231488#M468525</guid>
      <dc:creator>Terry L Johnson</dc:creator>
      <dc:date>2010-03-22T15:04:57Z</dc:date>
    </item>
    <item>
      <title>Re: diagmond performance hit every 290 secs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diagmond-performance-hit-every-290-secs/m-p/5231489#M468526</link>
      <description>Maybe you are running a bad and already replaced version?</description>
      <pubDate>Mon, 22 Mar 2010 15:39:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diagmond-performance-hit-every-290-secs/m-p/5231489#M468526</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2010-03-22T15:39:36Z</dc:date>
    </item>
    <item>
      <title>Re: diagmond performance hit every 290 secs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diagmond-performance-hit-every-290-secs/m-p/5231490#M468527</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Since 10.20 I've been answering DBA's questions about diagmond consuming, typically 5% of overall CPU consumption.  On a big box with a big database 5% is a big hit.&lt;BR /&gt;&lt;BR /&gt;You can turn off diags through /sbin/init.d/diagnostics off, and this will regain you resources.  But I would not do it.  Instead I would look to update my firmware and diagnostics bundles and review the problem.&lt;BR /&gt;&lt;BR /&gt;For its possible if your diags are out of date that your firmware is trying to send a message and no one is listening:  Diagnistics software does the listening.  Firmware does the sending.&lt;BR /&gt;&lt;BR /&gt;So if your firmware is out of date, you may have a problem and firmware can't notify anyone because it doesn't know how to.</description>
      <pubDate>Mon, 22 Mar 2010 16:42:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diagmond-performance-hit-every-290-secs/m-p/5231490#M468527</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2010-03-22T16:42:37Z</dc:date>
    </item>
    <item>
      <title>Re: diagmond performance hit every 290 secs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diagmond-performance-hit-every-290-secs/m-p/5231491#M468528</link>
      <description>stm is current spec for 11.11. hardware is 5470's 34440's&amp;amp; 4440's. Is we stop diagmond - no performace hiccups. we have them at 290 secs 5 mins &amp;amp; 10 min intervals</description>
      <pubDate>Mon, 22 Mar 2010 20:18:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diagmond-performance-hit-every-290-secs/m-p/5231491#M468528</guid>
      <dc:creator>Terry L Johnson</dc:creator>
      <dc:date>2010-03-22T20:18:41Z</dc:date>
    </item>
    <item>
      <title>Re: diagmond performance hit every 290 secs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diagmond-performance-hit-every-290-secs/m-p/5231492#M468529</link>
      <description>STM version should be A.65.00 (B.11.11.21.06 in swlist), EMS A.04.20.11&lt;BR /&gt;&lt;BR /&gt;Can you confirm?</description>
      <pubDate>Tue, 23 Mar 2010 04:24:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diagmond-performance-hit-every-290-secs/m-p/5231492#M468529</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2010-03-23T04:24:32Z</dc:date>
    </item>
    <item>
      <title>Re: diagmond performance hit every 290 secs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diagmond-performance-hit-every-290-secs/m-p/5231493#M468530</link>
      <description>resolved. it was tied to the RAD process for olar/r under diagmond control. Thanks everyone for your help</description>
      <pubDate>Tue, 23 Mar 2010 20:48:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diagmond-performance-hit-every-290-secs/m-p/5231493#M468530</guid>
      <dc:creator>Terry L Johnson</dc:creator>
      <dc:date>2010-03-23T20:48:16Z</dc:date>
    </item>
    <item>
      <title>Re: diagmond performance hit every 290 secs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diagmond-performance-hit-every-290-secs/m-p/5231494#M468531</link>
      <description>Thanks</description>
      <pubDate>Thu, 19 Aug 2010 17:07:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diagmond-performance-hit-every-290-secs/m-p/5231494#M468531</guid>
      <dc:creator>Terry L Johnson</dc:creator>
      <dc:date>2010-08-19T17:07:39Z</dc:date>
    </item>
  </channel>
</rss>

