You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
For both AC and DC sensitivity analysis, all factors end up in a "factor state" dense matrix. We already encountered 2 issues:
it sometimes can be greater that Java array size limit (which is the size of an integer)
it could lead a very high and uncontrollable memory consumption
What is the expected behavior?
We should be able to configure a "chunk size" so that internally DC and AC sensitivity analysis process factors by batches and so on limit the memory consumption even if lower performance.
What is the motivation / use case for changing the behavior?
Control memory consumption and allows to process a higher number of factors.
Please tell us about your environment:
PowSyBl Version: ...
OS Version: ...
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, spectrum, etc)
(if a question doesn't apply, you can delete it)
The text was updated successfully, but these errors were encountered:
flo-dup
changed the title
Limit memory consumption of sensisivity analysis
Limit memory consumption of sensitivity analysis
Nov 4, 2022
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
For both AC and DC sensitivity analysis, all factors end up in a "factor state" dense matrix. We already encountered 2 issues:
What is the expected behavior?
We should be able to configure a "chunk size" so that internally DC and AC sensitivity analysis process factors by batches and so on limit the memory consumption even if lower performance.
What is the motivation / use case for changing the behavior?
Control memory consumption and allows to process a higher number of factors.
Please tell us about your environment:
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, spectrum, etc)
(if a question doesn't apply, you can delete it)
The text was updated successfully, but these errors were encountered: