Preallocate global memory frames in advance #1987
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
phalcon
pushed a commit
that referenced
this pull request
Feb 7, 2014
Preallocate global memory frames in advance
ghost
deleted the
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently Phalcon preallocates one global memory frame that persists across requests. This PR changes this behavior by preallocating 10 memory frames (in one chunk). This results in fewer memory allocations during request processing.
Valgrind stats (
USE_ZEND_ALLOC=0 valgrind $(phpenv which php) /usr/bin/phpunit -c unit-tests/phpunit.xml)97.5k less memory allocations (this is not the cheapest operation), 9.1 MiB reused.