<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:clopez@igalia.com" title="Carlos Alberto Lopez Perez <clopez@igalia.com>"> <span class="fn">Carlos Alberto Lopez Perez</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Performance test IndexedDB/large-binary-keys.html creates a DB of more than 6GB"
href="https://bugs.webkit.org/show_bug.cgi?id=167616">bug 167616</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>rniwa@webkit.org
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Performance test IndexedDB/large-binary-keys.html creates a DB of more than 6GB"
href="https://bugs.webkit.org/show_bug.cgi?id=167616#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Performance test IndexedDB/large-binary-keys.html creates a DB of more than 6GB"
href="https://bugs.webkit.org/show_bug.cgi?id=167616">bug 167616</a>
from <span class="vcard"><a class="email" href="mailto:clopez@igalia.com" title="Carlos Alberto Lopez Perez <clopez@igalia.com>"> <span class="fn">Carlos Alberto Lopez Perez</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=167616#c1">comment #1</a>)
<span class="quote">> I think it's worth testing (It's provided huge benefit already)</span >
On the GTK+ perf bot this test is taking ~1620 seconds, which is beyond the 1200 global timeout for any step to be working without any output. So it causes the whole step to abort.
I will have to skip it on the GTK+ Perf bot until the test is changed to run faster, or some optimization is done on the WebKit/WebKitGTK+ code that makes it run faster.
Note also that I'm also proposing a patch on <a class="bz_bug_link
bz_status_NEW "
title="NEW - run-perf-tests timeout settings broken"
href="show_bug.cgi?id=167626">bug 167626</a> to bring back the 600 timeout value for any perf test. I don't think a unique test should take more than this (10 minutes) to run. We are already having 3+ hours long perf test steps, and if individual tests are allowed to run for more than 10 minutes we will be soon having much longer perf test steps.</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>