Jeremiah Senkpiel
Jeremiah Senkpiel
Also, for that last example, we're still using only about half the cpu cycles for the same number of requests as Node. ``` Performance counter stats for 'cargo run --release':...
I am going to caution that no_delay may be ideal for this benchmarking workload but _may_ not be ideal in the real world.
I want to take bottom-up perf stacks but don't know how to offhand with rust (and I am super busy).
Yeah that's a bug in femme. We should fix it, but something like https://crates.io/crates/json_env_logger should work. if you need custom keys you will probably need to write your own.
Oh, you are right, `json_env_logger` also doesn't do this correctly anymore. I forgot about that since I had to re-write that logger for internal use anyways (we wanted different field...
Is that message from `log::info!` or `trace::info!`?
Oh. I suppose that could be something like `log_level`.
I ended up doing this as the `"lambda-http"` for the Tide-wrapping framework I maintain for my employer: https://github.com/eaze/preroll#list-of-optional-add-on-features
Oh right. This is also available standalone as https://github.com/Fishrock123/tide-lambda-listener, which I completely forgot about.
I think if we have this, then `ModState` probably belongs in `http-types`? I am not sure if that would be confusing or not, given most of the other things there...