<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I don’t think 10 microsecond is a large lookahead; How big a system are you trying to simulate (as in the network size)? If the system is small, it may be hard to reduce the rollbacks as the #core increase.<div class=""><br class=""></div><div class="">Other things that can be tried:</div><div class="">1. nkp option = number of KPs; but default ROSS uses 16, but you can set it to (#total LPs)/(#cores) - i.e. make each LP has its own KP, which will prevent false rollbacks</div><div class="">2. gvt/batch size = you can try a small gvt frequency (like 4/8) and batch size (4/8).</div><div class=""><br class=""></div><div class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">---</div><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Nikhil Jain<br class="">Postdoctoral Fellow, Lawrence Livermore National Laboratory<br class=""><a href="mailto:nikhil.jain@acm.org" class="">nikhil.jain@acm.org</a>, <a href="http://nikhil-jain.github.io/" class="">http://nikhil-jain.github.io/</a></div></div></div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Jun 5, 2017, at 11:57, Jian Peng <<a href="mailto:jpeng10@hawk.iit.edu" class="">jpeng10@hawk.iit.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class="">Hi,<br class=""><br class=""></div> My simulation is having too many events rolled back, like 70%. It's still relatively small scale, 16 cores on 4 nodes, using optimistic scheduler. The result is attached.<br class=""><br class=""> Any general idea of reducing number of rollback events? I used the max-opt-lookahead option and set it to 10000. Is it still a large number?<br class=""><br class=""></div> Thanks!<br class=""></div>
<span id="cid:2F4A1176-21FB-4053-9408-F4DC07F681A2@ka.ltv"><rollback_result_1.png></span><span id="cid:0E0E128C-4B6F-40AD-9310-638784EFFE96@ka.ltv"><rollback_result_2.png></span>_______________________________________________<br class="">codes-ross-users mailing list<br class=""><a href="mailto:codes-ross-users@lists.mcs.anl.gov" class="">codes-ross-users@lists.mcs.anl.gov</a><br class="">https://lists.mcs.anl.gov/mailman/listinfo/codes-ross-users<br class=""></div></blockquote></div><br class=""></div></body></html>