You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The memory footprint for each client session is really huge right now. The main benefit is an increase of performance due to not having to allocate any tracking packet for QoS > 0 by allocating a 65536 array to track all possible concurrent inflight packets. A midway between having to malloc/free each new received packet that must be tracked till the transaction is completed and the current pre-allocate all solution would be great.
The text was updated successfully, but these errors were encountered:
The memory footprint for each client session is really huge right now. The main benefit is an increase of performance due to not having to allocate any tracking packet for QoS > 0 by allocating a 65536 array to track all possible concurrent inflight packets. A midway between having to
malloc/free
each new received packet that must be tracked till the transaction is completed and the current pre-allocate all solution would be great.The text was updated successfully, but these errors were encountered: