Vadim Kirilchuk

Hi, You are right, that most of the time all-in-one is great and my idea is not about removing it, but about having an additional views. If someone is interested...

I have found something interesting there. If add `doOnRequest(n -> log.info("Requested {}", n));` to the returned Flux, I can observe that by default `MonoSendMany` in reactor requests 1 and then...

Ok, s3-netty uses 8KB chunks instead of 8MB chunks which really helps here. So, here is what I think could be a solution: 1) Make reactor-netty request less than 128/64(refill),...

Alright, I just tried ```java S3AsyncClient.crtBuilder() .minimumPartSizeInBytes(1L * 1024 * 1024) // 1 MB ``` And even though parameter name is "uploadPartSize" and javadoc refers to Amazon Multipart Upload Limits,...

Hi @zoewangg, We can definitely play with that setting and this may reduce CRT read buffer, but the problem between reactor-netty and s3 client is that reactor-netty requests 128 part...

Hi, just posting an update on this one. We haven't experimented with `initialReadBufferSizeInBytes` yet. However, since we reduced part size, we transitively reduced the `initialReadBufferSizeInBytes`. 8MB => 80MB initial buffer...

I have finally submitted a feature request on the reactor-netty side, let's see what they say. [Reactor-netty feature request](https://github.com/reactor/reactor-netty/issues/3255)

Upd. I will be working on a PR for reactor-netty to make `request` configurable by property, gonna take some time. I am not sure if we want to close this...

@zoewangg good news, my pull request on the reactor-netty side was merged, once it's released it will be possible to keep default part size and simply reduce the prefetch size...

Hi @oogetyboogety, I am not sure that your issue is similar to mine. > backpressure mechanism not working in CRT It does work, initially I thought it's not working but...