Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow users to specify Packer's internal buf_size #547

Closed
wants to merge 1 commit into from
Closed

Allow users to specify Packer's internal buf_size #547

wants to merge 1 commit into from

Commits on Jul 18, 2023

  1. Allow users to specify Packer internal buf_size 

    Giving this flexibility to users means that internal reallocations can
be avoided if the buffer size is good enough, at the expense of
potentially allocating more memory than needed. This, together with
reusing a Packer object, means that multiple serialisations can end up
requiring no memory allocations other than the initial buffer creation,
which can be a big win in some situations.

The default value is still 1MB, making this backwards compatible.

Signed-off-by: Rodrigo Tobar <rtobar@icrar.org>
    @rtobar
    rtobar committed Jul 18, 2023
    Configuration menu
    Copy the full SHA
    edb61db View commit details
    Browse the repository at this point in the history