<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 - Potential Optimization - Avoid multiple recursions through the tree when calculating percent height"
href="https://bugs.webkit.org/show_bug.cgi?id=259538">259538</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Potential Optimization - Avoid multiple recursions through the tree when calculating percent height
</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>URL</th>
<td>https://jsfiddle.net/stwre9j6/show
</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>Layout and Rendering
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>ahmad.saleem792@gmail.com
</td>
</tr>
<tr>
<th>CC</th>
<td>bfulgham@webkit.org, simon.fraser@apple.com, zalan@apple.com
</td>
</tr></table>
<p>
<div>
<pre>HI Team,
Based on discussion with Alan (on Slack 1-1), I am exploring whether we can do this merge:
Blink Merge: <a href="https://chromium.googlesource.com/chromium/src.git/+/74e95b29247f21620cb94fdf72e7e1051fff80c2">https://chromium.googlesource.com/chromium/src.git/+/74e95b29247f21620cb94fdf72e7e1051fff80c2</a>
WebKit Source: <a href="https://searchfox.org/wubkat/source/Source/WebCore/rendering/RenderBox.cpp#731">https://searchfox.org/wubkat/source/Source/WebCore/rendering/RenderBox.cpp#731</a>
Performance Test: <a href="https://jsfiddle.net/stwre9j6/show">https://jsfiddle.net/stwre9j6/show</a>
_____
Safari Technology Preview 174:
Description: Measures performance of nested divs with percent values for height and max-height.
Time:
values 2.1645021645021645, 2.1645021645021636, 2.1668472372697734, 2.1691973969631246, 2.1810250817884405, 2.185792349726774, 2.183406113537118, 2.185792349726776, 2.185792349726776, 2.18579234972678, 2.1857923497267717, 2.183406113537118, 2.181025081788445, 2.178649237472767, 2.1834061135371137, 2.1739130434782696, 2.183406113537118, 2.183406113537118, 2.178649237472767, 2.1739130434782608 runs/s
avg 2.178910800251782 runs/s
median 2.182215597662779 runs/s
stdev 0.007440810283025579 runs/s
min 2.1645021645021636 runs/s
max 2.18579234972678 runs/s
and
Chrome Canary 117
Description: Measures performance of nested divs with percent values for height and max-height.
Time:
values 11472.47119099994, 11770.888071650446, 11833.069202510645, 11837.759282350935, 11977.542108546475, 12051.21767520943, 11902.231668720548, 11945.073990466863, 11837.759280952629, 11671.225739175741, 11867.549668639947, 11853.419764191982, 11746.198217140805, 11733.892090649078, 11733.8920904201, 11643.924626380767, 11462.197774693923, 11594.202897924757, 11478.349986619643, 11466.598413454549 runs/s
avg 11743.97318703496 runs/s
median 11758.543144395626 runs/s
stdev 178.66304514479208 runs/s
min 11462.197774693923 runs/s
max 12051.21767520943 runs/s
and Firefox Nightly 117 is similar ballpark to Chrome.
_________
Alan raised concern along the lines that the code can raise potential regressions, so I think I will continue to explore this locally but if someone has better and faster way to do it. Go ahead and knock it out of the park.
Thanks!</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>