Skip to content

Improvement #7928 : Make TempCacheLimit setting to be per-database, (not per-attachment) for SuperClassic. #7930

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 2 commits into from
Dec 19, 2023

Conversation

hvlad
Copy link
Member

@hvlad hvlad commented Dec 19, 2023

No description provided.

@hvlad hvlad self-assigned this Dec 19, 2023
return false;

const auto old = m_tempCacheUsage.fetch_add(size);
if (old + size > limit)
Copy link
Member

Choose a reason for hiding this comment

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

Isn't it problematic that someone trying to increase a size and not aquiring it, may temporary avoid that others increase they usage to values that otherwise would be valid?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, it is possible but I doesn't consider it as a problem.
If someone can't allocate the memory, it means the process have a much more serious issue currently.

…methods also.

Cache value of TempCacheLimit setting at global holder, as Dmitry suggests
@hvlad hvlad merged commit 6fed328 into v4.0-release Dec 19, 2023
@hvlad hvlad deleted the work/gh-7928 branch December 19, 2023 16:11
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.

Make TempCacheLimit setting to be per-database, (not per-attachment) for SuperClassic.
4 participants