-
Notifications
You must be signed in to change notification settings - Fork 202
Added "How to preserve RAM" #418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
XLinkIn / ImageManip are just part of the RAM consumers. I believe VideoEncoder consumes a lot of RAM, please try it out (using debugging to view RAM), measure the amount of RAM 1 VideoEncoder uses at eg. 1080P, 4k... and add results here, under eg. |
|
@Erol444 correct |
|
I will be finishing this PR, as Mojo doesn't have much time. New version below. Thoughts @themarpe / @szabi-luxonis ? |
themarpe
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of changes, LGTM from my perspective
| device.setLogLevel(dai.LogLevel.DEBUG) | ||
| device.setLogOutputLevel(dai.LogLevel.DEBUG) | ||
|
|
||
| There might be some memory issues when creating a larger number (around 10) of :ref:`ImageManip`, :ref:`XLinkIn` and other nodes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
having 10 imagemanip won't cause memory issues if frames are small - so I would leave this sentence out.

No description provided.