public GrpcServiceBuilder unsafeWrapRequestBuffers(boolean unsafeWrapRequestBuffers) {
        if (unsafeWrapRequestBuffers && useMethodMarshaller) {
            throw new IllegalStateException(
                    "'unsafeWrapRequestBuffers' and 'useMethodMarshaller' are mutually exclusive."
            );
        }
        this.unsafeWrapRequestBuffers = unsafeWrapRequestBuffers;
        return this;
    }
Enables unsafe retention of request buffers. Can improve performance when working with very large
(i.e., several megabytes) payloads.

<p><strong>DISCLAIMER:</strong> Do not use this if you don't know what you are doing. It is very easy to
introduce memory leaks when using this method. You will probably spend much time debugging memory leaks
during development if this is enabled. You will probably spend much time debugging memory leaks in
production if this is enabled. You probably don't want to do this and should turn back now.

<p>When enabled, the reference-counted buffer received from the client will be stored into
{@link RequestContext} instead of being released. All {@link ByteString} in a
protobuf message will reference sections of this buffer instead of having their own copies. When done
with a request message, call {@link GrpcUnsafeBufferUtil#releaseBuffer(Object, RequestContext)}
with the message and the request's context to release the buffer. The message must be the same
reference as what was passed to the service stub - a message with the same contents will not
work. If {@link GrpcUnsafeBufferUtil#releaseBuffer(Object, RequestContext)} is not called, the memory
will be leaked.

<p>Note that this isn't working if the payloads are compressed or the {@link SerializationFormat} is
{@link GrpcSerializationFormats#PROTO_WEB_TEXT}.
grpc/src/main/java/com/linecorp/armeria/server/grpc/GrpcServiceBuilder.java