-
Notifications
You must be signed in to change notification settings - Fork 75
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
Is it possible to receive message without deserialize? #175
Comments
You could hack your way around to it. This is where we attach the event listener that leads to deserialization. You could remove the listener we attach and add your own. There's one of these per publisher connection. Though if you have access, I'd recommend just adding another topic you can subscribe to. |
Thank you for the advice. I can add my on event listener on it now. However, the cpu usage does not reduce even it does not deserialize the message. |
The only other thing I can think of is just from pulling the messages off the wire - that happens here. PointCloud messages are generally pretty big and we don't reuse buffers so it could cause a lot of memory allocation. |
That issue seems to be recurring, and reusing buffers was also suggested here: #118 (comment). Seems like a good idea. |
I'd like to subscribe to a topic to serve as health checking.
However, the message being published is quite large and it leads to a high usage of CPU during deserialization of message which the content of the message doesn't matter to me.
Is there any way to receive the message without deserialization?
The text was updated successfully, but these errors were encountered: