<?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 CommandView SDM (sanmgr) memory hog in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/commandview-sdm-sanmgr-memory-hog/m-p/2658243#M381</link>
    <description>Anyone else notice that the sanmgr processes from CommandView SDM for the VA7400 chews up a great deal of memory. Our instance of sanmgr, specifically the kernel_th process, shows that it is using over 46MB of resident memory and almost 250MB of virtual memory. Seems like an awful lot of memory for a process that just keeps an eye on the disk arrays. Also, if you are running an older version of CommandView SDM, watch out for a memory leak!</description>
    <pubDate>Mon, 04 Feb 2002 15:51:58 GMT</pubDate>
    <dc:creator>Joe Giegel</dc:creator>
    <dc:date>2002-02-04T15:51:58Z</dc:date>
    <item>
      <title>CommandView SDM (sanmgr) memory hog</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/commandview-sdm-sanmgr-memory-hog/m-p/2658243#M381</link>
      <description>Anyone else notice that the sanmgr processes from CommandView SDM for the VA7400 chews up a great deal of memory. Our instance of sanmgr, specifically the kernel_th process, shows that it is using over 46MB of resident memory and almost 250MB of virtual memory. Seems like an awful lot of memory for a process that just keeps an eye on the disk arrays. Also, if you are running an older version of CommandView SDM, watch out for a memory leak!</description>
      <pubDate>Mon, 04 Feb 2002 15:51:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/commandview-sdm-sanmgr-memory-hog/m-p/2658243#M381</guid>
      <dc:creator>Joe Giegel</dc:creator>
      <dc:date>2002-02-04T15:51:58Z</dc:date>
    </item>
  </channel>
</rss>

