Skip to content

ISO8601TimeSpanFormatter to use local byte[] array, as opposed to renting from pool. #4503

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.

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

Merged
merged 1 commit into from
Mar 27, 2020

Conversation

codebrain
Copy link
Contributor

The minimum buffer size that can be rented from the shared memory pool is 65535 bytes. This amount of memory for the purposes of serializing the day component of a string timespan is excessive. This commit changes the procedure to use a local byte array

Adds test for max size of 64bit value.

…om pool.

The minimum buffer size that can be rented from the shared memory pool is 65535 bytes. This amount of memory for the purposes of deserialising the day component of a string timespan is excessive. This commit changes the procedure to use a local byte array.
@codebrain codebrain requested a review from russcam March 20, 2020 05:12
@codebrain
Copy link
Contributor Author

Closed in favor of: #4509

@codebrain codebrain closed this Mar 25, 2020
@codebrain codebrain changed the title DateTimeFormatter to use local byte[] array, as opposed to renting from pool. ISO8601TimeSpanFormatter to use local byte[] array, as opposed to renting from pool. Mar 27, 2020
@codebrain codebrain reopened this Mar 27, 2020
@codebrain codebrain marked this pull request as ready for review March 27, 2020 02:40
Copy link
Contributor

@russcam russcam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Some failing integration tests here that look related to running against a 7.7 snapshot. Be good to open an issue for / fix

@codebrain codebrain merged commit 12cb326 into 7.x Mar 27, 2020
@codebrain codebrain deleted the research/datetimeformatter-mem-use branch March 27, 2020 07:05
github-actions bot pushed a commit that referenced this pull request Mar 27, 2020
…om pool. (#4503)

The minimum buffer size that can be rented from the shared memory pool is 65535 bytes. This amount of memory for the purposes of deserialising the day component of a string timespan is excessive. This commit changes the procedure to use a local byte array.
github-actions bot pushed a commit that referenced this pull request Mar 27, 2020
…om pool. (#4503)

The minimum buffer size that can be rented from the shared memory pool is 65535 bytes. This amount of memory for the purposes of deserialising the day component of a string timespan is excessive. This commit changes the procedure to use a local byte array.
codebrain added a commit that referenced this pull request Mar 27, 2020
…om pool. (#4503) (#4522)

The minimum buffer size that can be rented from the shared memory pool is 65535 bytes. This amount of memory for the purposes of deserialising the day component of a string timespan is excessive. This commit changes the procedure to use a local byte array.

Co-authored-by: Stuart Cam <stuart.cam@elastic.co>
codebrain added a commit that referenced this pull request Mar 27, 2020
…om pool. (#4503) (#4523)

The minimum buffer size that can be rented from the shared memory pool is 65535 bytes. This amount of memory for the purposes of deserialising the day component of a string timespan is excessive. This commit changes the procedure to use a local byte array.

Co-authored-by: Stuart Cam <stuart.cam@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants