home | log | search | bash | stats | wiki


Matches for oomkill, 32 total results Sorted by newest | relevance

20-03-2016 00:14:20  <mod6>   asciilifeform: about that error I saw, thanks for your insight. I looked the other system logs to see if that was the issue, but didn't see the OOMKILL like I have before. So I was thinking it wasn't related to that somehow. Anyway, good to know.

19-03-2016 18:54:56  <asciilifeform>   i still marvel at the idiocy of the existence of oom-without-oomkill

18-12-2015 14:08:40  <*>   mircea_popescu has set the goal at 30 days w/o oomkill on 16gb box, and even that took some engineering.

24-11-2015 02:33:27  <asciilifeform>   so far this looks like an ordinary oomkill.

17-08-2015 20:52:35  <ascii_field>   thestringpuller: looks like an oomkill to me

30-07-2015 00:34:52  <trinque>   because the latter results in oomkill iirc

14-07-2015 19:18:52  <ascii_field>   rather than 'oomkill because retarded'

16-05-2015 19:02:55  <mod6>   Now, currently, I'm running a very similar test with v0.5.3.1-RELEASE (as a baseline) without your OrphanageThermonuke patch included... it did oomkill once, yesterday.

16-05-2015 19:02:01  <mod6>   so yes, the first performance test was me running v0.5.3.1-RELEASE with Orphanage_Thermonuke patched in. Performance test conducted with `vmstat 1` & `nmon -f s3 -c1000000`. During this test the entire sync process completed without any oomkill.

16-05-2015 18:51:03  <mod6>   <+asciilifeform> ;;later tell mod6 so orphanage-thermonuke has never oom-crashed in your tests ? << nope! it was pretty exciting to see it get all the way through full sync without oomkill.

16-05-2015 06:39:37  <mod6>   Addtionally, I 100% agree, if anyone else should test either of these and capture anything surrounding the OOMKILL either in the v0.5.3.1-RELEASE or a patched version of v0.5.3.1-RELEASE, please let us know.

16-05-2015 06:38:29  <mod6>   <+asciilifeform> mod6: please post any data you may have collected at the moment of the oomkill << so just to reiterate here, the current perf test I'm running is with the v0.5.3.1-RELEASE which oomkill'd (as it's known to do). I'll post the nmon charts, log, and vmstat log. no core file was created. However, as a reminder, the previous perf test that I ran with v0.5.3.1-RELEASE+{asciilifeform_orphanage_thermonuke.patch}(http://thebitcoin.foun

16-05-2015 05:33:29  <decimation>   asciilifeform: on another project I've been chasing an oomkill that happens ... when acpi is turned on

16-05-2015 05:32:42  <asciilifeform>   this goes for anyone else who got oomkill with orphanage-thermonuke specifically, on a box with ad libitum ram

16-05-2015 05:31:51  <asciilifeform>   mod6: please post any data you may have collected at the moment of the oomkill

16-05-2015 05:30:39  <assbot>   Logged on 16-05-2015 03:14:16; mod6: im getting closer to my v0.5.3.1-RELEASE perf full bc sync baseline being finished; currently on block 304969 -- it did oomkill today though, and didn't see it for like 8-9 hours :/

16-05-2015 03:14:16  <mod6>   im getting closer to my v0.5.3.1-RELEASE perf full bc sync baseline being finished; currently on block 304969 -- it did oomkill today though, and didn't see it for like 8-9 hours :/

12-05-2015 00:32:03  <asciilifeform>   because the former is unbounded, but will never oomkill the process

01-02-2015 21:11:44  <asciilifeform>   danielpbarron: that's a standard oomkill

30-01-2015 16:23:12  <assbot>   17 results for 'oomkill' : http://s.b-a.link/?q=oomkill

  Next Page »