<?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: disk bottleneck in XP128 in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-bottleneck-in-xp128/m-p/3209700#M168309</link>
    <description>This is a common "problem" when using Glance (or any other host-based) tools to measure IO on high performance devices like disk arrays. The only thing Glance knows (or can know) is that a tremendous amount of IO is going through what it sees as one physical device. It has no way of knowing that what it sees as a disk (or LUN) is actually comprised of multiple physical disks within the array. Almost certainly, you have no real problem --- just the appearance of one. &lt;BR /&gt;&lt;BR /&gt;I have seen cases where admins would divide a VG into several LUN's just so things would appear better to Glance although the actual I/O rate was no better.&lt;BR /&gt;</description>
    <pubDate>Thu, 04 Mar 2004 13:06:29 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2004-03-04T13:06:29Z</dc:date>
    <item>
      <title>disk bottleneck in XP128</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-bottleneck-in-xp128/m-p/3209698#M168307</link>
      <description>I have a XP128 attached to my HP-UX with 4 optic fibers and Autoptah. The Xp128 use disk arrays for the LUNS and have a cache of 12 GB &lt;BR /&gt;In the GlancePlus Disk Graph some LUNS (DISK) have 100% when i copy large files (1 or 2 GB) to filesystem in this disk.&lt;BR /&gt;Why the LUNS of XP128 have 100% only a copy files?&lt;BR /&gt;Is there a disk bottleneck or Filesystem  bottleneck?&lt;BR /&gt;</description>
      <pubDate>Thu, 04 Mar 2004 13:01:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-bottleneck-in-xp128/m-p/3209698#M168307</guid>
      <dc:creator>XJIM</dc:creator>
      <dc:date>2004-03-04T13:01:16Z</dc:date>
    </item>
    <item>
      <title>Re: disk bottleneck in XP128</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-bottleneck-in-xp128/m-p/3209699#M168308</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Utilization at 100% doesn't necessarily mean there is a bottleneck. But if you see Qlen (in the same window) on that disk, then there may be. This means the system is pushing faster than the disk subsystem can handle.&lt;BR /&gt;&lt;BR /&gt;-Sri&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 04 Mar 2004 13:05:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-bottleneck-in-xp128/m-p/3209699#M168308</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2004-03-04T13:05:59Z</dc:date>
    </item>
    <item>
      <title>Re: disk bottleneck in XP128</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-bottleneck-in-xp128/m-p/3209700#M168309</link>
      <description>This is a common "problem" when using Glance (or any other host-based) tools to measure IO on high performance devices like disk arrays. The only thing Glance knows (or can know) is that a tremendous amount of IO is going through what it sees as one physical device. It has no way of knowing that what it sees as a disk (or LUN) is actually comprised of multiple physical disks within the array. Almost certainly, you have no real problem --- just the appearance of one. &lt;BR /&gt;&lt;BR /&gt;I have seen cases where admins would divide a VG into several LUN's just so things would appear better to Glance although the actual I/O rate was no better.&lt;BR /&gt;</description>
      <pubDate>Thu, 04 Mar 2004 13:06:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-bottleneck-in-xp128/m-p/3209700#M168309</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2004-03-04T13:06:29Z</dc:date>
    </item>
  </channel>
</rss>

