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.

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

BAAS-24348: estimate mem usage for gomap and goslice when over thresholds #110

Merged
merged 9 commits into from
Jan 18, 2024

Conversation

Gabri3l
Copy link

@Gabri3l Gabri3l commented Jan 10, 2024

This is something we already do for arrays and objects so I ported over the logic. I did some renaming just to be consistent with other mem usage functions (I don't feel strongly about it though).

object_goslice.go Show resolved Hide resolved
object_gomap.go Show resolved Hide resolved
@Gabri3l
Copy link
Author

Gabri3l commented Jan 16, 2024

Took the chance to handle the division by 0 for array and base objects

Copy link

@nathantfrank nathantfrank left a comment

Choose a reason for hiding this comment

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

LGTM

@Gabri3l Gabri3l merged commit c85b024 into mongodb-forks:realm Jan 18, 2024
2 of 6 checks passed
@Gabri3l Gabri3l deleted the BAAS-24348 branch January 18, 2024 21:38
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