Skip to content

Utilization exceeds multiplicity #6

@gcasale

Description

@gcasale

In this model:

<?xml version="1.0" encoding="utf-8"?>
<lqn-model xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="test_LQN_4" xsi:noNamespaceSchemaLocation="lqn.xsd">
   <processor multiplicity="2" name="P1" quantum="0.001" scheduling="ps" speed-factor="1">
      <task multiplicity="50" name="T1" scheduling="ref" think-time="2">
         <entry name="E1" type="NONE"/>
         <task-activities>
            <activity bound-to-entry="E1" call-order="STOCHASTIC" host-demand-cvsq="1" host-demand-mean="0.1" name="AS1">
               <synch-call calls-mean="1" dest="E2"/>
            </activity>
         </task-activities>
      </task>
      <task multiplicity="50" name="T2" scheduling="fcfs">
         <entry name="E2" type="NONE"/>
         <task-activities>
            <activity bound-to-entry="E2" call-order="STOCHASTIC" host-demand-cvsq="1" host-demand-mean="0.05" name="AS2">
               <synch-call calls-mean="5" dest="E3"/>
            </activity>
            <reply-entry name="E2">
               <reply-activity name="AS2"/>
            </reply-entry>
         </task-activities>
      </task>
   </processor>
   <processor multiplicity="3" name="P2" quantum="0.001" scheduling="ps" speed-factor="1">
      <task multiplicity="25" name="T3" scheduling="fcfs">
         <entry name="E3" type="NONE"/>
         <task-activities>
            <activity bound-to-entry="E3" call-order="STOCHASTIC" host-demand-cvsq="1" host-demand-mean="0.02" name="AS3"/>
            <reply-entry name="E3">
               <reply-activity name="AS3"/>
            </reply-entry>
         </task-activities>
      </task>
   </processor>
</lqn-model>

LQNS 6.2.29 on linux gives at P1 <result-processor utilization="2.26678"/> that exceeds the multiplicity of the PS station.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions