Graph Engine improvements to avoid OutOfMemory #997
rmohan20
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi everyone!
We've made some significant changes around optimizing Graph Engine to decrease the probability of an OutOfMemory error.
🚀 🚀 🚀 🚀
If you were running into OutOfMemory errors before, with v3.10.0 you should start having
scanner:run:dfa
reach completion with a set of usable results. However, you may also see someLimitReached
rows in your results. These are highly complex paths that Graph Engine had to stop processing so that it could complete processing the remaining code.We've added recommended steps in our documentation about how you can iteratively get complex paths analyzed. Also, if you are curious to understand the reasoning, have a look at the last section of our FAQ that explains how these steps reduce the occurrence of OutOfMemory errors.
Let us know in this thread how these changes work for you. 🧵
We are eager to hear your questions/ideas/feedback.
Beta Was this translation helpful? Give feedback.
All reactions