'[Webkit-unassigned] [Bug 151670] New: Fix the graphics benchmark complexity bounds adjustment'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       webkit-unassigned
Subject:    [Webkit-unassigned] [Bug 151670] New: Fix the graphics benchmark complexity bounds adjustment
From:       bugzilla-daemon () webkit ! org
Date:       2015-11-30 20:45:34
Message-ID: bug-151670-2851 () https ! bugs ! webkit ! org/
[Download RAW message or body]

--1448916320.1e2cABfA1.11590
Date: Mon, 30 Nov 2015 12:45:20 -0800
MIME-Version: 1.0
Content-Type: text/plain

https://bugs.webkit.org/show_bug.cgi?id=151670

            Bug ID: 151670
           Summary: Fix the graphics benchmark complexity bounds
                    adjustment
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Animations
          Assignee: webkit-unassigned@lists.webkit.org
          Reporter: sabouhallawa@apple.com
                CC: dino@apple.com

The test complexity bounds (min-max values) are used to prevent the test FPS from \
fluctuating. We always make sure the current complexity of the test is within these \
bounds. These bounds are the min-max values of the test complexity starting from the \
beginning of the first overshoot till the end of the following undershoot of the FPS.

We need also to make sure that the bounds are large enough to allow some flexibility. \
This is helpful when the difference between the lower and upper bounds is very small. \
I think it is enough to make sure the lower bound is at least 90% of the upper bound. \
The bounds are negative in the case of graphics benchmark since the relationship \
between the test complexity and FPS is reverse proportional. So we need to apply the \
adjustment to the "absolute" minimum bound which is (min if min < 0) or (max if max < \
0).

-- 
You are receiving this mail because:
You are the assignee for the bug.
--1448916320.1e2cABfA1.11590
Date: Mon, 30 Nov 2015 12:45:20 -0800
MIME-Version: 1.0
Content-Type: text/html

<html>
    <head>
      <base href="https://bugs.webkit.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Fix the graphics benchmark complexity bounds adjustment"
   href="https://bugs.webkit.org/show_bug.cgi?id=151670">151670</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Fix the graphics benchmark complexity bounds adjustment
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>WebKit
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>WebKit Nightly Build
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Unspecified
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Unspecified
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>Normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P2
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>Animations
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>webkit-unassigned&#64;lists.webkit.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>sabouhallawa&#64;apple.com
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>dino&#64;apple.com
          </td>
        </tr></table>
      <p>
        <div>
        <pre>The test complexity bounds (min-max values) are used to prevent the test \
FPS from fluctuating. We always make sure the current complexity of the test is \
within these bounds. These bounds are the min-max values of the test complexity \
starting from the beginning of the first overshoot till the end of the following \
undershoot of the FPS.

We need also to make sure that the bounds are large enough to allow some flexibility. \
This is helpful when the difference between the lower and upper bounds is very small. \
I think it is enough to make sure the lower bound is at least 90% of the upper bound. \
The bounds are negative in the case of graphics benchmark since the relationship \
between the test complexity and FPS is reverse proportional. So we need to apply the \
adjustment to the &quot;absolute&quot; minimum bound which is (min if min &lt; 0) or \
(max if max &lt; 0).</pre>  </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>
--1448916320.1e2cABfA1.11590--

_______________________________________________
webkit-unassigned mailing list
webkit-unassigned@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-unassigned

[prev in list] [next in list] [prev in thread] [next in thread] 