-
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
bad deserialize perfomance with image data array #117
Comments
I believe you've stumbled on a case where we didn't update the on-the-fly message code to work the same way as the pre-generated messages. The generated messages specifically deal with uint8 arrays by slicing out a section of the overall message buffer rather than iterating over the length of the array. |
@panshengjie thanks for reporting. Do you have a canonical code example to reproduce this? That would help us fix this more promptly. |
@chfritz I was subscirbed to a image topic, with type sensor_msgs/Image, and found a significant rise on cpu usage |
for uint8 array, I've forced converting buffer to Uint8Array . BUT this is not a general resolution, may lead to compatibility issues |
I've check the source code, In
reading buildin-type array one-by-one using buffer.readUInt8 ,eating-up the CPU.
The text was updated successfully, but these errors were encountered: