<?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: WLM vs PRM in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/wlm-vs-prm/m-p/2500391#M883108</link>
    <description>The PRM configuration that WLM generates always has PRM CPU capping enabled.  By doing so, WLM will always be able to control the amount of CPU given to each workload.  With no goals defined, the WLM configuration can simply be viewed as a PRM configuration with fixed CPU caps.&lt;BR /&gt;&lt;BR /&gt;In the absence of performance goals, WLM can still prioritize workloads on a system.&lt;BR /&gt;&lt;BR /&gt;You can create service level objectives (SLOs) with a CPU usage goal.  These goals do not require external metrics and will try to give a workload more CPU when it is busy and less when it is idle.&lt;BR /&gt;&lt;BR /&gt;You can also use the weight keyword to indicate the relative importance of each workload, then turn on the distribute_excess tunable to have WLM equitably share the CPU cycles amoung the workloads.</description>
    <pubDate>Mon, 05 Mar 2001 22:16:26 GMT</pubDate>
    <dc:creator>Steven Landherr</dc:creator>
    <dc:date>2001-03-05T22:16:26Z</dc:date>
    <item>
      <title>WLM vs PRM</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/wlm-vs-prm/m-p/2500390#M883107</link>
      <description>If i assume i'm not using Goals Based SLOs.&lt;BR /&gt;If WLM is only a modifier of the prmconf, how can we define priorities if WLM acts only when CPU usage is 100% (prm fonctionnality without capping).&lt;BR /&gt;&lt;BR /&gt;Regards</description>
      <pubDate>Fri, 02 Mar 2001 15:30:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/wlm-vs-prm/m-p/2500390#M883107</guid>
      <dc:creator>Leroy_1</dc:creator>
      <dc:date>2001-03-02T15:30:23Z</dc:date>
    </item>
    <item>
      <title>Re: WLM vs PRM</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/wlm-vs-prm/m-p/2500391#M883108</link>
      <description>The PRM configuration that WLM generates always has PRM CPU capping enabled.  By doing so, WLM will always be able to control the amount of CPU given to each workload.  With no goals defined, the WLM configuration can simply be viewed as a PRM configuration with fixed CPU caps.&lt;BR /&gt;&lt;BR /&gt;In the absence of performance goals, WLM can still prioritize workloads on a system.&lt;BR /&gt;&lt;BR /&gt;You can create service level objectives (SLOs) with a CPU usage goal.  These goals do not require external metrics and will try to give a workload more CPU when it is busy and less when it is idle.&lt;BR /&gt;&lt;BR /&gt;You can also use the weight keyword to indicate the relative importance of each workload, then turn on the distribute_excess tunable to have WLM equitably share the CPU cycles amoung the workloads.</description>
      <pubDate>Mon, 05 Mar 2001 22:16:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/wlm-vs-prm/m-p/2500391#M883108</guid>
      <dc:creator>Steven Landherr</dc:creator>
      <dc:date>2001-03-05T22:16:26Z</dc:date>
    </item>
  </channel>
</rss>

