-
Notifications
You must be signed in to change notification settings - Fork 90
Open
Labels
Description
When using request-response, the internal connection between the servers and clients requires a lot of memory. It is not yet clear if this is a bug or that the worst case assumptions somehow pile up here and cause this memory overhead.
It can already be observed in the simple request-response example from the repository. See:
52k iox2_0354a209029e7d094a819e2d4030ea331e6caaf0_90711141441948140518990960335.data
1.2k iox2_0354a209029e7d094a819e2d4030ea331e6caaf0_91328914599941840254787409767.data
1.7k iox2_305ad9523c6b202364d581359ec3d2c5743e42e7_be37df3dea2dab734fe80c6e2ca532b0a6f34ec6.dynamic
19k iox2_b9fc73e5c1f646968758453273c6c65cb372831b_90711141441948140518990960335_91328914599941840254787409767.connection
374 iox2_b9fc73e5c1f646968758453273c6c65cb372831b_91328914599941840254787409767_90711141441948140518990960335.connection
Where one connection has a size of 19k while the other has just 374 bytes
So the task is:
- Find out if it is the connection from client to server (for requests) or from server to client (for responses).
- Explore what is causing the issue on this large connection size.
- Fix it - if possible