<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 - Performance test IndexedDB/large-binary-keys.html creates a DB of more than 6GB"
href="https://bugs.webkit.org/show_bug.cgi?id=167616">167616</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Performance test IndexedDB/large-binary-keys.html creates a DB of more than 6GB
</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>Tools / Tests
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>clopez@igalia.com
</td>
</tr>
<tr>
<th>CC</th>
<td>achristensen@apple.com, beidson@apple.com, bugs-noreply@webkitgtk.org, lforschler@apple.com
</td>
</tr>
<tr>
<th>Blocks</th>
<td>165567
</td>
</tr></table>
<p>
<div>
<pre>The Performance test IndexedDB/large-binary-keys.html was timing out on the GTK+ performance bot since it was added on <a href="https://trac.webkit.org/changeset/209499">https://trac.webkit.org/changeset/209499</a>.
The main reason was that our Performance bot was using a dedicated /tmp volume with 2GB of space, and this test requires at least ~ 6.5 GB of free disk space on /tmp to successfully run.
$ du -hs /tmp/WebKitTestRunner-pGQSwk
6.6G /tmp/WebKitTestRunner-pGQSwk
$ find /tmp/WebKitTestRunner-pGQSwk
/tmp/WebKitTestRunner-pGQSwk
/tmp/WebKitTestRunner-pGQSwk/LocalStorage
/tmp/WebKitTestRunner-pGQSwk/Databases
/tmp/WebKitTestRunner-pGQSwk/Databases/IndexedDB
/tmp/WebKitTestRunner-pGQSwk/Databases/IndexedDB/file__0
/tmp/WebKitTestRunner-pGQSwk/Databases/IndexedDB/file__0/large-string-keys-DB-0
/tmp/WebKitTestRunner-pGQSwk/Databases/IndexedDB/file__0/large-string-keys-DB-0/IndexedDB.sqlite3-wal
/tmp/WebKitTestRunner-pGQSwk/Databases/IndexedDB/file__0/large-string-keys-DB-0/IndexedDB.sqlite3-shm
/tmp/WebKitTestRunner-pGQSwk/Databases/IndexedDB/file__0/large-string-keys-DB-0/IndexedDB.sqlite3
/tmp/WebKitTestRunner-pGQSwk/Cache
/tmp/WebKitTestRunner-pGQSwk/Cache/Version 11
/tmp/WebKitTestRunner-pGQSwk/Cache/Version 11/Blobs
/tmp/WebKitTestRunner-pGQSwk/Cache/Version 11/salt
$ ls -1sh /tmp/WebKitTestRunner-pGQSwk/Databases/IndexedDB/file__0/large-string-keys-DB-0
total 6.6G
201M IndexedDB.sqlite3
50M IndexedDB.sqlite3-shm
6.3G IndexedDB.sqlite3-wal
I have already fixed the issue with getting out of space on the GTK+ perf bot. It has now 30GB for /tmp that should be enough.
So, I open this bug mainly to ask if testing the performance on such monster databases (6.6GB) is something representative of real world use cases or it is something worth testing?
The test also takes a lot to complete, between 30 and 45 minutes.</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>