<div dir="ltr">-WD<div><br></div><div>Ya, I'm going to recommend we look into this and see if other options give us some improvement</div><div><br></div><div><br></div><div>-David</div><div><br></div><div>The current benchmark run takes about 10 days to fully solve, which is about on par with our longest/largest 'production' problem. </div>
<div><br></div><div>The machines are on a UPS, but it is more for power conditioning than uptime. With three of these machines in the rack running all out, the largest rackmount units are only good for a few minutes. However, the program does 'checkpoint' itself at certain intervals, so we will loose some data with a power loss, but usually no more than a few hours worth on these really long solves. </div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 16, 2013 at 6:28 PM, David <span dir="ltr"><<a href="mailto:ainut@knology.net" target="_blank">ainut@knology.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I had completely forgotten about the overhead of atime and did not know the practicality of noatime. Good catch, Charles.<br>
<br>
So I recommend that you use a filesystem on the ssd's that does not use journaling, and set the ssd drive directories with (as root) :<br>
<br>
format the SSD's with ext2 (fat32 is not recommended for high speed usage but may not matter with ssd's and only two files);<br>
<br>
then,<br>
<br>
[root@machine /root]#*chattr* -R +A /dirofSSDtempdata/<br>
(after reformat, of course.)<br>
<br>
<br>
Caveat: without journaling, ensure you have a good battery backup APS on the system. You probably already have that for something that runs for WEEKS!<br>
<br>
Also, I hope whoever wrote the program made it re=entrant with little loss of time in case the system did crash, for whatever reason.<br>
<br>
<br>
David M.<br>
<br>
<br>
<br>
Charles Moye wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
and set noatime?<div class="im"><br>
<br>
<br>
On Mon, Dec 16, 2013 at 9:45 AM, David <<a href="mailto:ainut@knology.net" target="_blank">ainut@knology.net</a> <mailto:<a href="mailto:ainut@knology.net" target="_blank">ainut@knology.net</a>>> wrote:<br>
<br>
Can't remember if ext4 uses journaling but if it does, you'll get<br>
better times if you can turn it off.<br>
<br>
<br>
<br>
Stephan Henning wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
Wow, nice.<br>
<br>
-WD, I've gone in and checked, and at least on the SSD array,<br>
it's ext4.<br>
<br>
<br>
On Mon, Dec 16, 2013 at 7:01 AM, Matt <<a href="mailto:brimstone@the.narro.ws" target="_blank">brimstone@the.narro.ws</a><br></div><div class="im">
<mailto:<a href="mailto:brimstone@the.narro.ws" target="_blank">brimstone@the.narro.ws</a><u></u>>> wrote:<br>
<br>
On 12/15/2013 10:37 PM, Arthur wrote:<br>
> What did mailman do?<br>
<br>
Arthur,<br>
<br>
Mailman's default setting for digests is to send them out<br>
every 30KB.<br>
People don't trim messages like the bad old days; Ethan's<br>
response email<br>
after yours is 35KB alone. I upped the setting to 10MB, which<br>
is Gmail's<br>
inbound limit if I recall correctly.<br>
<br>
#matt<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
General mailing list<br>
<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a><br></div>
<mailto:<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.<u></u>makerslocal.org</a>><div class="im"><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/<u></u>mailman/listinfo/general</a><br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
General mailing list<br></div>
<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a> <mailto:<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.<u></u>makerslocal.org</a>><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/<u></u>mailman/listinfo/general</a><br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
General mailing list<br>
<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a> <mailto:<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.<u></u>makerslocal.org</a>><div class="im">
<br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/<u></u>mailman/listinfo/general</a><br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
General mailing list<br>
<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/<u></u>mailman/listinfo/general</a><br>
</div></blockquote><div class="HOEnZb"><div class="h5">
<br>
<br>
______________________________<u></u>_________________<br>
General mailing list<br>
<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/<u></u>mailman/listinfo/general</a><br>
</div></div></blockquote></div><br></div>