Java Azure Function App Blob Trigger – Memory Not Released After Invocation - Stack Overflow

admin管理员组

文章数量:1304889

I am running a Java Azure Function App with a Blob Trigger on an App Service Plan. However, I have noticed that after each function invocation and successful completion, the memory usage remains high and does not decrease. This behavior persists even when the function becomes idle.

Are there specific JVM configurations or Azure Function settings to enforce better memory cleanup?

I am running a Java Azure Function App with a Blob Trigger on an App Service Plan. However, I have noticed that after each function invocation and successful completion, the memory usage remains high and does not decrease. This behavior persists even when the function becomes idle.

Are there specific JVM configurations or Azure Function settings to enforce better memory cleanup?

• java
• memory-leaks
• azure-functions

Share Improve this question Follow asked Feb 3 at 21:21 Denis KisinaDenis Kisina 40488 silver badges2323 bronze badges 1

• Provide your function code. – Pravallika KV Commented Feb 7 at 3:39

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 1

• Turn off Always on under FunctionApp=>Settings=>Configuration=>General Settings and check if the memory usage is still high:

• Check the memory usage of the function under Function App=>Diagnose and solve problems=>Memory Analysis:

• Try setting -ioty.noPreferDirect: false and ioty.maxDirectMemory: -1, refer GitHub issue.

I have created a Java Blob Triggered Azure function App with App Service Plan and observed the memory usage.

Uploaded two files to the Storage Container and the metrics of function App is below: Metrics:

And the function App started to utilize the memory after restarting it.

本文标签： Java Azure Function App Blob Trigger – Memory Not Released After InvocationStack Overflow