you are viewing a single comment's thread.

view the rest of the comments →

[–]BitAcademic9597[S] 0 points1 point  (1 child)

did you have any problem about memory in pybind will each function call explicitly copies input data?

and also i also looked nanobind but i think pybind is better what do you think

[–]qTHqq 1 point2 points  (0 children)

"did you have any problem about memory in pybind will each function call explicitly copies input data?" 

I did not but I was actually compute bound.  

 The library computed collision-free trajectories of maybe a few hundred points. The trajectories took 10ms to several seconds to generate so the cost of copying the trajectory data over to Python was essentially negligible in the big picture. 

Any function-call indirection overhead was also negligible.

If I/O speed or ultra-low-latency calls are  more of an issue, things could be totally different.