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
Xadd qs could lazy allocate the pooled chunk, on demand, instead of eagerly allocate them.
This could be implemented using a plain int field to count the already pooled chunks: this plain int field could be used while appending new chunks, given that is a single writer code.
The interesting thing is that it could save all the configured allocations to ever happen, depending on the load.
In addition it could allow to reuse the max number of allocated chunks (under the max load) by targeting an unbounded number of pooled chunks.
The text was updated successfully, but these errors were encountered:
Xadd qs could lazy allocate the pooled chunk, on demand, instead of eagerly allocate them.
This could be implemented using a plain int field to count the already pooled chunks: this plain int field could be used while appending new chunks, given that is a single writer code.
The interesting thing is that it could save all the configured allocations to ever happen, depending on the load.
In addition it could allow to reuse the max number of allocated chunks (under the max load) by targeting an unbounded number of pooled chunks.
The text was updated successfully, but these errors were encountered: