<html>#1321: Collisions in executable cache directory
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Ian Hinder</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>development version</td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>SimFactory</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>Caching the executable (currently about 1.1 GB when compiling all thorns and with debug symbols) in order to reduce disk space usage becomes mostly moot once the first checkpoint is written: even the lowest resolution checkpoint for a vacuum run of mine is 2.0 GB per checkpoint file, and there are 64 checkpoint files per checkpoint. </p>
<p>So it really only matters for things like test runs (or the testsuites) where no checkpoints are being written. </p>
<p>The cache also uses hard-links across directories which not all file systems like / support (BeeGFS is one of them). </p>
<p>Do we need the cache? Removing it would remove all issues associated with it.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/1321/collisions-in-executable-cache-directory'>https://bitbucket.org/einsteintoolkit/tickets/issues/1321/collisions-in-executable-cache-directory</a></p>
</html>