forked from docs/doc-exports
Chen, Junjie
dac566cf2f
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com> Co-authored-by: Chen, Junjie <chenjunjie@huawei.com> Co-committed-by: Chen, Junjie <chenjunjie@huawei.com>
12 lines
832 B
HTML
12 lines
832 B
HTML
<a name="functiongraph_03_0868"></a><a name="functiongraph_03_0868"></a>
|
|
|
|
<h1 class="topictitle1">Why Does a Function Use More Memory Than Estimated and Even Trigger the Out of Memory Alarm?</h1>
|
|
<div id="body0000001402357841"><ol id="functiongraph_03_0868__ol28239310583"><li id="functiongraph_03_0868__li1682315319585">Event parsing and cache consume extra memory during function invocation.</li><li id="functiongraph_03_0868__li38241831589">After the invocation is complete, reclaimed memory is often put in the internal pool instead of back to the OS, resulting in high memory usage. This is more obvious in the case of high concurrency.</li></ol>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="functiongraph_03_0346.html">Function Execution FAQs</a></div>
|
|
</div>
|
|
</div>
|
|
|