Image transport very slow when using png compression
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
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.
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.
- Dominant language
- C++
- Stars
- 154
- Forks
- 258
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from ros-perception/image_common
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ros-perception/image_common#346 · 1 reaction ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
ros-perception/image_common#286 · 1 comment ·
-
[ROS2] CameraInfoManager set_camera_info service callback returns without updating saved cal dataOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ros-perception/image_common#131 ·
-
Topic remaps are recursed multiple times in image_transportPossibly taken @paneendrakumar0 claimed this 9 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
ros-perception/image_common#435 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
ros-perception/image_common#434 · 4 comments · 3 reactions ·
All issues in ros-perception/image_common
Similar issues
-
status:needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
PX4/PX4-Autopilot#29698 ·
Maintainers usually reply within 1 day
-
go perft exits when EvalFile is unavailablePossibly taken @Muawiya-contact claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
official-stockfish/Stockfish#7292 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
arvidn/libtorrent#9149 ·
Maintainers usually reply within 1 day
-
Upstream report: MSVC rejects a designated initializer in a dependent template argument (C2131)Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
rhalbersma/tabula#72 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
esp8266/Arduino#9342 · 2 comments ·
Maintainers usually reply within 1 day