NOTES: Solver RAM allocation can be done with a single parameter, called solram. If the Creo Simulate Structure/Thermal engine is the only memory-intensive application running on your computer, performance will usually be best if you set solram equal to half of your machine RAM. For example, solram 512 is a good choice for a machine with 1024 MB of RAM.
If you are running other memory-intensive applications on your computer, decrease the solram allocation accordingly. For example, set solram to 0.25 times machine RAM if you are running two large applications at once. However, you often can run two large jobs faster one after another than if you try to run both jobs at once.
The purpose of solram is to reduce the amount of disk I/O. If you set solram too high, performance will usually suffer, even on machines with very large RAM, because there will not be enough machine RAM for other important data. For example, Creo Simulate allocates many large, non-solver memory areas that will cause excessive swapping unless you leave enough spare machine RAM. You must also leave enough RAM for the operating system to do disk caching. Disk caching improves filesystem performance by holding file data in RAM for faster access. Setting solram to half machine RAM is usually the best compromise between reducing the amount of disk I/O, and leaving enough machine RAM for disk caching and for other data..
The auto-generated statement you've shared is a very old one that should be replaced. I believe this description is almost word-for-word the recommendation RASNA used when the tool was RASNA Mechanica Structure (late 80's to mid 90's). If I remember correctly, "solram" was an environmental variable you would set to force the amount of machine RAM to use. When was the last time anybody used a computer with 1 GB of RAM to run FEA? In fact, when was the last time a decent computer came with 1 GB RAM? There are much better recommendations/guidelines found in the help for Simulate, under "Memory Usage - Different Scenarios". If you review the "Checkpoints" log file following a run, you can find useful information (and the boilerplate statement shared originally by "fstopelli"). In the following text, you'll see some information (red box) that would help provide estimates for what you should use - 2 MB is the minimum recommended for this problem, but 50 MB would be enough to hold the entire global matrix:
The details to set the RAM are found through these icon picks:
The "Run Settings" dialog will be displayed where you may enter a value for solver RAM: