Skip to content
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

C++ Implementation possibility #6

Open
piyush-m0 opened this issue Oct 22, 2024 · 2 comments
Open

C++ Implementation possibility #6

piyush-m0 opened this issue Oct 22, 2024 · 2 comments

Comments

@piyush-m0
Copy link

I think the performance while using eCAL with foxglove would prove significantly better if the bridge was implemented in C++, similar to ecal-rerun-bridge.

@KerstinKeller
Copy link
Contributor

Do you encounter specific problems with the bridge?
So far, I haven't seen any performance problems. We have recently fixed some internal memory leaks for the Python binding, which we will be releasing bugfix releases for (eCAL 5.13.3, eCAL 5.12.7).

When I initially implemented this bridge, I also tried implementing it in C++, but it was a lot more difficult to build, and I didn't see any benefits over the python version (latency, throughput, ...), so I dropped the C++ implementation.

@piyush-m0
Copy link
Author

I did notice the FPS drops with rerun while using python. Hence I believe while using high FPS topic visualisation, writing it in C++ would make it more resilient.

I am interested in contributing to the C++ implementation if there is any initiated. Python while having a GIL might cause bottlenecks when handling more topics at a higher FPS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants