Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
I've been evaluating Nemo's streaming performance by running Nexmark queries.
When running Query 7 with 150,000events/s input rate, sometimes Nemo fully consumes CPU resource at some point and throws OOM. This happens intermittently and it looks like a bug. Sometimes Nemo just uses ~50% cpu use constantly and processes the inputs without exception.