Replies: 1 comment 2 replies
-
I haven't read any discussion regarding the performance of bindgen other than the impact of enabling the attribute detection feature which slowed bindgen considerably on larger C++ headers. If you're deduplicating a lot of items you could use the Maybe it would make sense to profile bindgen and check where are we spending more time and why. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have several (5-10+) ~6000 line headers I want to generate bindings for. (These headers have a lot of the same types but I post-process the bindings from bindgen to deduplicate them.) My question is what is the best practice to efficiently generate bindings for these files? Obviously I can stick them all in one bindgen call, but that seems to really slow down as I add headers. My second thought was to split up the bindgen invocations and run them in parallel, but with fewer files this seems slower than just doing it all in one call.
Is there some kind of best number of lines/files where it makes sense to split invocations across threads? Or is bindgen already multi threaded and this is pointless?
Beta Was this translation helpful? Give feedback.
All reactions