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

DSO+T example has very large memory footprint #156

Open
trevorhardy opened this issue Jul 23, 2024 · 2 comments
Open

DSO+T example has very large memory footprint #156

trevorhardy opened this issue Jul 23, 2024 · 2 comments
Labels

Comments

@trevorhardy
Copy link
Collaborator

The DSO+T cases for one month typically have a memory footprint of 20-40 GB. In some cases, though, we're seeing memory footprints of ~100GB.

@trevorhardy
Copy link
Collaborator Author

trevorhardy commented Oct 14, 2024

HELICS vs FNCS is showing a over 3x memory footprint for GridLAB-D (15GB vs 4.5 GB). In Python processes running at the same time, we see the opposite: FNCS has about a 2x memory footprint as compared to HELICS. All of these are running inside a Docker environment (we don't think this is relevant). We see the results when running the "Rates" memory example and is very repeatable.

@trevorhardy
Copy link
Collaborator Author

As best as we can tell, this does not occur when running on PNNL's HPC where the memory is limited to 64GB. When running these cases on our other machines, they are taking over 100 GB.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant