<?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: How does the Tru64 OS use vmemory vs. memory ulimit settings? in Operating System - Tru64 Unix</title>
    <link>https://community.hpe.com/t5/operating-system-tru64-unix/how-does-the-tru64-os-use-vmemory-vs-memory-ulimit-settings/m-p/3338873#M10422</link>
    <description>memory is to generic, datasize, stack size?&lt;BR /&gt;In case of a memory problem it is important to know what kind of memory is required. That's the reason software vendors offers tuning information for their applications.&lt;BR /&gt;&lt;BR /&gt;So please specify what kind of memory is required. If you are a gambler increase all kind of memory of start program with root privileges to check if it will run within the hard limits.&lt;BR /&gt;</description>
    <pubDate>Thu, 22 Jul 2004 12:12:34 GMT</pubDate>
    <dc:creator>Ralf Puchner</dc:creator>
    <dc:date>2004-07-22T12:12:34Z</dc:date>
    <item>
      <title>How does the Tru64 OS use vmemory vs. memory ulimit settings?</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/how-does-the-tru64-os-use-vmemory-vs-memory-ulimit-settings/m-p/3338872#M10421</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Can someone tell me the significant differences between the ulimit categories:- "memory" and "vmemory"?&lt;BR /&gt;&lt;BR /&gt;Clearly "vmemory" relates to the amount of virtual memory a process may hold at any one time.&lt;BR /&gt;&lt;BR /&gt;Is "memory" the amount of physical memory that a process may hold - *or* is it the total memory (physical + virtual) that a process may hold ?&lt;BR /&gt;&lt;BR /&gt;We have low ulimit memory settings - and are experiencing "Out of memory/Failed to allocate memory" messages from some of our hungry processes.&lt;BR /&gt;&lt;BR /&gt;Do we update the "memory" limit, the "vmemory" limit or both?&lt;BR /&gt;&lt;BR /&gt;I can see that the "vmemory" limit is limited itself by a system kernel parameter.&lt;BR /&gt;&lt;BR /&gt;Can someone please provide a description for how these values are used in relation to how the OS manages resources given to a process ?&lt;BR /&gt;&lt;BR /&gt;Many thanks for any info you can give&lt;BR /&gt;Regards&lt;BR /&gt;Paul McGrath</description>
      <pubDate>Thu, 22 Jul 2004 11:32:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/how-does-the-tru64-os-use-vmemory-vs-memory-ulimit-settings/m-p/3338872#M10421</guid>
      <dc:creator>paulmcgrath</dc:creator>
      <dc:date>2004-07-22T11:32:42Z</dc:date>
    </item>
    <item>
      <title>Re: How does the Tru64 OS use vmemory vs. memory ulimit settings?</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/how-does-the-tru64-os-use-vmemory-vs-memory-ulimit-settings/m-p/3338873#M10422</link>
      <description>memory is to generic, datasize, stack size?&lt;BR /&gt;In case of a memory problem it is important to know what kind of memory is required. That's the reason software vendors offers tuning information for their applications.&lt;BR /&gt;&lt;BR /&gt;So please specify what kind of memory is required. If you are a gambler increase all kind of memory of start program with root privileges to check if it will run within the hard limits.&lt;BR /&gt;</description>
      <pubDate>Thu, 22 Jul 2004 12:12:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/how-does-the-tru64-os-use-vmemory-vs-memory-ulimit-settings/m-p/3338873#M10422</guid>
      <dc:creator>Ralf Puchner</dc:creator>
      <dc:date>2004-07-22T12:12:34Z</dc:date>
    </item>
  </channel>
</rss>

