erts: Report the effective atom_limit - #11364
Merged
Merged
Conversation
erts_index_init() grows its table one INDEX_PAGE_SIZE page at a time and only checks the limit when allocating a new page, so the effective limit is the requested value rounded up to a whole number of pages. Store that rounded value in t->limit so that erlang:system_info(atom_limit) reports the limit actually enforced, like process_limit and port_limit do, rather than echoing back the raw +t value.
Contributor
CT Test Results 3 files 136 suites 49m 57s ⏱️ Results for commit 672b8e8. ♻️ This comment has been updated with latest results. To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts// Erlang/OTP Github Action Bot |
Contributor
Author
|
Suggested here: #11264 (comment) |
sverker
approved these changes
Aug 3, 2026
sverker
added
enhancement
testing
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
erts_index_init() grows its table one INDEX_PAGE_SIZE page at a time and only checks the limit when allocating a new page, so the effective limit is the requested value rounded up to a whole number of pages. Store that rounded value in t->limit so that erlang:system_info(atom_limit) reports the limit actually enforced, like process_limit and port_limit do, rather than echoing back the raw +t value.