feat(clients): NetworkReceive memory optimization

[surajdarade]

Fixes #2962 [ Enhancement/Optimization ]

Clean MemoryPool implementation at NetworkReceive:

• Lazy creation of buffer via MemoryPool
• readFrom() - Allocation Failure - return head (prevent attempt to a payload without memory)
• readFrom() - Readable execution flow
• close() - Buffer ownership optimization - removed buffer != EMPTY_BUFFER (before buffer was not allocated through the MemoryPool, now being allocated through MemoryPool, MemoryPool now becomes single owner for all payload buffers)

[surajdarade]

Any update on this? @superhx , @Gezi-lzq

[superhx]

@surajdarade Thank you for your PR. The expectation of the ISSUE is to add a new MemoryPool implementation to optimize the memory usage of NetworkReceive.

[surajdarade]

Thanks for redirecting. Will refactor as per the intended requirement now.

[surajdarade]

Have a look on this proposed optimization, let me know what can we improved, what revamp is needed.

[superhx]

Have a look on this proposed optimization, let me know what can we improved, what revamp is needed.

Hi, the requirement is to implement a new MemoryPool to optimize memory usage. Currently, SocketServer.memoryPool uses MemoryPool.NONE by default.

[github-actions]

This PR is being marked as stale since it has not had any activity in 90 days. If you would like to keep this PR alive, please ask a committer for review. If the PR has merge conflicts, please update it with the latest from trunk (or appropriate release branch)

If this PR is no longer valid or desired, please feel free to close it. If no activity occurs in the next 30 days, it will be automatically closed.