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
One performance pitfall during Xpansion workflow is the writing/reading of problem on disk.
By linking to Simulator directly and passing problems in memory we could prevent reading and writing.
Awnser: For large study, could we have RAM issue holding all problems in memory
If yes to the previous question: find an appropriate strategy
Have simulator expose a lib returning problems
Have simulator install properly for clients (resolve include properly)
One performance pitfall during Xpansion workflow is the writing/reading of problem on disk.
By linking to Simulator directly and passing problems in memory we could prevent reading and writing.
Useful PR for reference:
AntaresSimulatorTeam/Antares_Simulator#1081
#568
The text was updated successfully, but these errors were encountered: