Help Center> FunctionGraph> User Guide (Kuala Lumpur Region)> FAQs> Function Execution FAQs> Why Does a Function Use More Memory Than Estimated and Even Trigger the Out of Memory Alarm?

Updated on 2023-07-06 GMT+08:00

View PDF

Why Does a Function Use More Memory Than Estimated and Even Trigger the Out of Memory Alarm?

Event parsing and cache consume extra memory during function invocation.
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.

Parent topic: Function Execution FAQs

Previous topic: How Do I Read the Request Header of a Function?

Next topic: How Do I Check the Memory Usage When Seeing "runtime memory limit exceeded"?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.