OOM Keep your mits off!

[Guest_imported]

I have this little c-proggie that's is, I admit, a total resource hog with huge arrays & many cycles. The OOM is killing it after random intervals... normally, in a multi-user environment, this would be a good thing. However, the job will only be run on a machine(s) temporarily dedicated to it.

OK, I've gotta chunk the job eventually, however doing this will severely compromise efficiency (during the reconstitution phase) so I want to make the job chunks as large as
possible.

Whew, all that & no question yet... The question is: In your experience, what is the best way to torque back the OOM? Even better, if it's possible, what is the best way to temporarily get that beastie to back off a bit?

TIA

 

[Guest_imported]

looks like OOM is everyone else's friend The Lone Ranger rides off on his own quixotic quest to slay this daemon.

 

[cluelessNewbie]

You can create a private swap are via a memory mapped file. man 3 the mmap & msync functions. You can write your "huge arrays" to a file and then memory map that file & play with the data all you want.

Provided you're not trying to write beowolf code & keep it all on the same box. You shouldn't need to chunk the job for data size. AND you can very easily multi-process the job (like with a dual-processor box) thru this method.