ros-perception / ros-perception/image_common
Image transport very slow when using png compression
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 153
- Forks
- 253
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
I'm developing a ROS driver for a camera which is using image transport for publishing the images.
When using png as the format for the compressed stream the frame rate decreases drastically. For jpeg I manage to publish 30 fps while for png I only manage to publish 4 fps when setting the png_level to 1 (which is the minimum). I know this issue is due to the CPU intensive png encoding and is something not directly related to image_transport. However, is there any other approach I could use to increase the frame rate while using png compression?
I thought about using a pool of workers with an image transport publisher each, but it didn't work as each image transport publisher must have a different topic name.
The "best" solution I can think of is to encode the image in multiple workers (using cv::imencode) and later or publish them using normal publishers instead of image transport.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the image_transport publisher behavior described in the issue, including the separate topic requirement for each publisher. Compare the proposed worker-pool approach using cv::imencode with publishing through normal publishers. Done should be a documented or implemented approach that increases PNG frame rate without requiring conflicting topic names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- robotics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100