Michael Davis

Forgot to clean up and makes sure things were wrapped properly, whoops! I've also added a test case to assert that we handle the effects in the proper order.

I'm a bit busy at the moment so I haven't given this a proper look but 20-40ms does seem quite high. I'm also surprised it's cheaper to write than read....

`stream!` and `read_stream` use essentially the same code path. The difference is that `stream!` uses `Stream.unfold/2` to repeatedly read from the server so that you can eventually read even very...

I believe the C# client reads with effectively no limit and it's set rather low in Spear. You can try tuning that option but I don't think it should have...

Sorry for the long delay! Things have been hectic lately. I took a look at those packet captures and looking with a filter of `http2.header` I'm seeing similar numbers between...

I can reproduce the timing differences. With a similar Elixir script: ```elixir Mix.install [{:spear, path: "."}, {:jason, "~> 1.0"}] {:ok, conn} = Spear.Connection.start_link(connection_string: "esdb://localhost:2113?tls=false") stream_name = "Document:134" start1 = :erlang.monotonic_time()...

I was curious about the chatty WINDOW_UPDATE frames so I took a look into Mint. Mint sends a WINDOW_UPDATE both for the request stream (i.e. the ReadReq) and for the...

Feel free to give #93 a try. This is not a very high priority problem for me so I will probably not look at this again for a little while....

Despite what I said above about putting this down for a while, I gave this another look today 😄 Here's a script of what I was thinking about above: perf_test.exs...

I took a look into the `Mint.HTTP2.request/5` part and there are some easy wins to speed that up: https://github.com/elixir-mint/mint/pull/423 I also looked at splitting the timing up for `receive/1` and...