<html>#2882: Running BBH with CarpetX with CPUs: High memory consumption and low performance
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Alejandra Gonzalez</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></td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>CarpetX</td></tr>
</table>
<p>Comment (by Liwei Ji):</p>
<p>I’m not surprised with this speed without subcycling.<br>
You can do the following to improve a bit</p>
<ol>
<li>Turn off calc_ADMRHS_vars, it’s not required for BBH simulations.</li>
<li>Use 2 OMP instead of 7. It’s the best number for me. You should try different OMP yourself.</li>
<li>You can also play a bit with the par <code>max_tile_size_x</code> while keeping <code>max_tile_size_y/z</code> small. I didn’t see big speed difference for myself, but you can still try.</li>
</ol>
<p>For the memory issue, if you are using Z4c from the development branch of my fork, it has 5 copies of state vector for the purpose of subcycling. You can use the main branch instead. </p>
<p><span class="ap-mention" data-atlassian-id="557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22">@Roland Haas</span> could you take a look at the <code>run_cactus.sh</code> and see if there anything suspicions?</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2882/running-bbh-with-carpetx-with-cpus-high'>https://bitbucket.org/einsteintoolkit/tickets/issues/2882/running-bbh-with-carpetx-with-cpus-high</a></p>
</html>