Skip to content
This repository has been archived by the owner on Jun 13, 2019. It is now read-only.

Suggestions on measuring python <=> rust overhead if any #40

Open
softprops opened this issue Jul 14, 2018 · 1 comment
Open

Suggestions on measuring python <=> rust overhead if any #40

softprops opened this issue Jul 14, 2018 · 1 comment

Comments

@softprops
Copy link
Contributor

Hi. I've been working on some extensions of crowbar that put a focus on apigateway and recently started putting together some notes to advertise performance expectations. My tests are somewhat limited to what happens after crowbar translates python objects to serde Json values.

Do you have any suggests on how I could measure the cost more completely or if you've already down this your self the approach you took? I'm thinking I could take my .so file and create my own python handler that dynamically loads it in it's event handler and just delegate the handling while timing what happens in between. Thoughts?

@iliana
Copy link
Owner

iliana commented Oct 2, 2018

Would it make sense for the python <=> rust overhead to be benchmarked in cpython-json, since that seems to be where all the magic is happening?

That crate doesn't have any benchmarks I believe and could probably use some.

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

No branches or pull requests

2 participants