Allocated memory #1386
Replies: 2 comments 3 replies
-
@spaulins-usgs and @aleaf will probably have some ideas, but one thing you might want to try is to use external files, and binary if possible. Flopy won't try to load them unless it needs to. |
Beta Was this translation helpful? Give feedback.
-
@marcowhites, the MFSimulation object directly or indirectly contains all the data (MFSimulation contains MFModel and MFPackage objects which contain MFPackage, MFBlock, and MFData objects). @langevin-usgs's suggestion of storing the data in external files should help. If you are not already doing so, I also recommend using a 64 bit version of python instead of a 32 bit version, which should give you a higher maximum of allocated memory. @langevin-usgs, I could possibly add an "unload_data" method to MFSimulation, which unloads all data from memory except what is necessary to run the simulation. The MFSimulation object would then be in an "unloaded" state, and would either return appropriate error messages if the user tried to access data or perhaps automatically reload the simulation when data access is attempted. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I am running multiple instances of a big transient MF6 model within Flopy on a HPC and I am encountering some issue with amount of memory required by Flopy and the number of nodes I can use. I wonder if others have had the same issue. Is there a way to free up RAM after the write_simulation() command. I can run the MF6 outside Python, but I wonder if this is the only way. Does the MFSimulation object (flopy.mf6.modflow.mfsimulation) contain all the data and therefore becomes bigger and bigger as we add data for the MF6 packages?
Thanks
Marco Bianchi (BGS)
Beta Was this translation helpful? Give feedback.
All reactions