Nick Vatamaniuc

That would neat to have @sergey-safarov, thanks for the link to https://www.rabbitmq.com/blog/2022/05/31/flame-graphs Our Erlang version is high enough and we can set `+JPperf true` and limit scheduler threads (`+S 4`)...

That could work but it may be simpler to start with some synthetic benchmarks, for example I found a few k6 scripts floating around: https://gist.github.com/nickva/d5312248635534315e76d25b31a86faa : a simple get,put,post for...

Try tweaking these config values: ```ini [chttpd] disconnect_check_msec = 30000 disconnect_check_jitter_msec = 15000 ``` For instance, make `disconnect_check_msec = 300000` and see if it makes a difference. This could mean...

@big-r81 thanks! I think we'd only want to decrement it if the request was a changes request otherwise we'd end up with negative value soon enough if we have other...

Yeah something like a periodically updated metrics gauge of streaming connection counts. We have a dedicated monitor process for each one of those... Another idea is to abandon the inc/dec...

> continuous changes req is the only request that could in theory never end, whereas all the others do, so there's not as strong a need to count them in-flight...

In Apache CouchDB we always clear and re-create both the runtime and the context so the simplification would be welcome for us not have to deal with both.

``` /* new API with a single realm */ { JSContext *ctx; const char *eval1 = "print(\"hello\")"; ctx = JS_NewContext(); JS_Eval(ctx, eval1, strlen(eval1), "", 0); JS_FreeContext(ctx); } ``` ^ At...