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
Hi there, would it be possible to add an option/API that messages received via a subscription make use of the memory pool? We're currently evaluating a scenario where we'd receive rather large data blocks. As of now those blocks cause allocations on the LOH (MatchResult -> TryGetPubSubPayload -> AsRedisValue) which in turn leads to costly Gen2 collections.
We could probably work around it for now with StringGetLeaseAsync and read the data through some polling mechanism.
The text was updated successfully, but these errors were encountered:
Hi there, would it be possible to add an option/API that messages received via a subscription make use of the memory pool? We're currently evaluating a scenario where we'd receive rather large data blocks. As of now those blocks cause allocations on the LOH (
MatchResult -> TryGetPubSubPayload -> AsRedisValue
) which in turn leads to costly Gen2 collections.We could probably work around it for now with
StringGetLeaseAsync
and read the data through some polling mechanism.The text was updated successfully, but these errors were encountered: