On Sun, 2020-03-22 at 22:08 -0700, Waldek Kozaczuk wrote: > > > On Monday, March 23, 2020 at 12:36:52 AM UTC-4, rickp wrote: > > Looks to me like its trying to allocate 40MB but the available > > memory > > is 10GB, surely? 10933128KB is 10,933MB > > > > I misread the number - forgot about 1K. > > Any chance you could run the app outside of production with memory > tracing enabled - > https://github.com/cloudius-systems/osv/wiki/Trace-analysis-using-trace.py#tracing-memory-allocations > (without --trace-backtrace) for while? And then we can have a better > sense of what kind of allocations it makes. The output of trace > memory-analyzer would be really helpful.
I can certainly run that local with locally generated workloads, which should be close enough - but we've never managed to trigger the oom condition that way (other than by really constraining the memory artificially). It should be close enough though - let me see what I can do. Rick -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to osv-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osv-dev/77725fd3d095c86e37648713ab4bd3185a496500.camel%40rossfell.co.uk.
