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
One thing I did for speed is to require the length for each chunk, so that we can avoid needing to re-patch the length after the chunk is done writing.
However, for some workloads, it may be cheaper to do the extra IO than it would be to pre-compute the length. It shouldn't be too tricky to support this flow.
The documentation for this new function should describe the implementation so that users can make a judgement about whether they want to try to compute the chunk sizes or whether they want to let OkayWAL fill in the details for them.
The text was updated successfully, but these errors were encountered:
One thing I did for speed is to require the length for each chunk, so that we can avoid needing to re-patch the length after the chunk is done writing.
However, for some workloads, it may be cheaper to do the extra IO than it would be to pre-compute the length. It shouldn't be too tricky to support this flow.
The documentation for this new function should describe the implementation so that users can make a judgement about whether they want to try to compute the chunk sizes or whether they want to let OkayWAL fill in the details for them.
The text was updated successfully, but these errors were encountered: