Uploaded image for project: 'Product Technical Learning'
  1. Product Technical Learning
  2. PTL-9721

RH442 ch07s02: step 6.2 & 6.3 is not explained enough to get what is happening

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • RH442 - RHEL8.0-en-1-20190828
    • RH0050L, RH442
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • 7
    • en-US (English)
    • RH442 Sprint 5, RH442 Sprint 6, RH442 Sprint 7

      Please fill in the following information:


      URL: https://rol.redhat.com/rol/app/courses/rh442-8.0/pages/ch07s02
      Reporter RHNID:           chetan-rhls  
      Section title:

      Guided Exercise: Configuring CPU Scheduling Policies and Tunables

       

      Language: English

      Issue description: RH442 ch07s02: step 6.2 & 6.3 is not explained enough to get what is happening. Why was 6th task not allowed to execute ? which is the sixth task / pid ? 6395 ? How was 5th task allowed then ? This step needs more explanation to understand wha are we observing and why it is happening like this ? Is it correct that : In the example that you provided, the deadline scheduler is configured to allow a total utilization of 30%. However, the actual utilization of the deadline tasks is 174.10256530%. This means that the deadline scheduler is overloaded but then how 5th task was allowed. Also the scripts used to calculate is a nightmare to look or understand. we expect a lot of explanation in step 6.3 like for each pid how current and configured util has so varied high ranges but suddenly it ends at lab finish command. 

       

      Steps to reproduce:

       

      Expected result:

        1. image-2023-09-27-04-08-43-802.png
          306 kB
          Chetan Tiwary
        2. image-2023-09-27-04-15-15-178.png
          713 kB
          Chetan Tiwary

              glsbugs-hybridcloud@redhat.com PTL - RHEL Team
              chetan-rhls Chetan Tiwary
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: