PDA

View Full Version : FG Memory use & activated modules



MarianDz
November 4th, 2016, 10:34
Yesterday I make some tests and maybe somebody will be interested in.

This test was made for better imagination and as answer on question "Is my 4GB memory enough to open more modules, guides and adverntures at once?"
And for these of you who wants to know answer how many modules can be in same time opened without memory fail errors. So continue in reading :).

During all my tests I always close program and open again for more accurate results.
Avoid this way counting and stacking cached files from previous opened modules which can in finale deform results.
Cached files shows third column (gray color), after closing module still ocupy some memory space.
Are subtracted from total amount of memory taken with module enabled and memory state after disable current module.

This is informational only because opening images, maps, more windows, start playing, etc. ... results in another needs and memory - grows up!
I only made opening FantasyGrounds still in same conditions (no addons, extensions), then Activate module(-s) and compare informations about actuall used memory from my Task manager - processes.

Now I know that is safe runs all my modules at same time without memory overload ;o)
At all FG takes cca 1,2GB from my memory and still exist reserves for operatins system and opening another work.

Have on mind 32-bit (x86) platform utilise max 3.2GB at total! not as 64-bit (x64) where OS has pushed limit for memory which can be utilised above 16GB.
And of course I see no reason why have all modules oppened and decals loaded. From today exist better modules which need your memory space for example D&D Volo's Guide to Monsters or D&D Map Pack Volume 1, etc... :p

Thank you for reading, and wish you all have a nice FG sessions

* all my values which I used in my table depends on many things and may vary 100 K +/-.

damned
November 4th, 2016, 13:55
Hi MarianDZ I think Trenloe has published some numbers - FG on a 32bit windows will only access about 1.5GB RAM and on 64bit around 3GB RAM. FG itself is not 64bit.

ddavison
November 4th, 2016, 14:31
Thanks for posting that.

One of the major drivers with the overhaul of the list windows was specifically to support people opening up every single module that is compatible with a ruleset at once. We still have some issues with tokens in the current architecture where it loads them all into memory, but this was a big step forward that cut down on overall memory usage and actually sped up the interface. Our internal testing was done with every single WOTC and third-party 5E module open at once.

MarianDz
November 4th, 2016, 19:27
Thank you both "damned" and "ddavison" for your time write me here.

Trenloe
November 4th, 2016, 21:15
Interesting data - thanks for taking the time to test, put it together and share with us. :)