--
You received this message because you are subscribed to the Google Groups "netlogo-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to netlogo-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/netlogo-users/CAHs8kB8AY0niJk7-opOGc9iziHGbb3y15d9FAhthFQRL%3DOFZKw%40mail.gmail.com.
--
We have tested NetLogo with models that use hundreds of megabytes of RAM and they work fine. We haven’t tested models that use gigabytes of RAM, though. Theoretically it should work, but you might hit some limits that are inherent in the underlying Java VM and/or operating system (either designed-in limits, or bugs).
The NetLogo engine has no fixed limits on size. By default, though, NetLogo ships with a one-gigabyte ceiling on how much total RAM it can use. If your model exceeds that limit, you’ll get an OutOfMemoryError dialog.
If you are using BehaviorSpace, note that doing runs in parallel will multiply your RAM usage accordingly.
Each platform contains “.cfg” files containing JVM settings. There is one cfg file for each sub-application (NetLogo, NetLogo 3D, HubNet Client, etc.) Although the file location varies by platform, the process for changing it is the same. Locate the section of the file that looks like the following:
[JVMOptions]
# there may be one or more lines, leave them unchanged
-Xmx1024m
# there may be one or more lines, leave them unchanged
Modify the value immediately following -Xmx
, changing it to the amount of
space you need, save the file, and restart NetLogo. Platform specific notes
follow:
C:\Program Files\NetLogo 6.2.0\app
,
unless you are running 32 bit NetLogo on a 64 bit Windows, then it will be
in C:\Program Files (x86)\NetLogo 6.2.0\app
./Application/NetLogo 6.2.0/NetLogo 6.2.0.app/Contents/Java/NetLogo.cfg
For
NetLogo 3D and the other applications, you will find the file in the
corresponding location for each application package. You can reach the cfg
file by control-clicking the application in the Finder and choosing “Show
Package Contents” from the popup menu.
Please note that depending on your version of Mac OS X, changing the cfg file may break application signing. If this happens, follow Apple’s directions on this page to temporarily allow apps from “Anywhere”, run NetLogo once, then restore the setting to “Mac App Store and Identified Developers”.
netlogo-6.2.0/app
folder after untarring.By default, Mac builds of NetLogo bundle a 64-bit JVM, which should be able to
make use of as much memory as the lesser of available system memory and the
value following -Xmx
. Windows and Linux will bundle a 32-bit or 64-bit JVM,
depending on which version you have downloaded. It is recommended that you
install 64-bit NetLogo on all 64-bit operating systems for best performance.
--
--
To view this discussion on the web visit https://groups.google.com/d/msgid/netlogo-users/CACv-4rAjaLFAc5Ko%2Bm0DLgkma354-9o1udCvwby-aU4rUvSOow%40mail.gmail.com.
On 9 Oct 2021, at 11:36 pm, Michael Tamillow <mikaelta...@gmail.com> wrote:
This comes off as a general inquiry into Netlogo, but I’m curious what inspired it.
To view this discussion on the web visit https://groups.google.com/d/msgid/netlogo-users/AA5F8CD4-7615-497F-8150-1950F9AF0A7C%40gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/netlogo-users/62093980-6DB7-475C-BD7F-5B973A6FAAD5%40gmail.com.
On Oct 9, 2021, at 9:33 PM, John Chen <yuehanc...@u.northwestern.edu> wrote: