Loading all GAP packages
39 views
Skip to first unread message
Antonio Rojas
Apr 30, 2021, 3:05:41 AM4/30/21
to sage-devel
Hi,
On a fresh run of the GAP interface, Sage caches a GAP workspace which loads every single GAP package on the system. While this might be OK with Sage's trimmed-down version of gap_packages, if using a system GAP install with all optional packages installed this can take a massive amount of memory (~1GB with all packages included in the 4.11.1 tarball), which in many casses surpasses the default gap_memory_pool_size value, causing crashes. This will become a common issue once #29644 is merged.
I don't think it is realistic to expect a user to need every single optional package. Should this preloading be limited to a selected number of packages (eg. those loaded in GAP by default)? Or just let users load the packages they need on demand?
Vincent Delecroix
Apr 30, 2021, 3:21:11 AM4/30/21
to sage-...@googlegroups.com
Hi,
Does your remark applies to both the pexpect GAP interface and libgap?
The two options you propose sound reasonable. I might have a preference
towards GAP defaults since the user would be able to modify it via
a .gaprc file.
Vincent
The two options you propose sound reasonable. I might have a preference
towards GAP defaults since the user would be able to modify it via
a .gaprc file.
Vincent
Antonio Rojas
Apr 30, 2021, 3:35:15 AM4/30/21
to sage-devel
El viernes, 30 de abril de 2021 a las 9:21:11 UTC+2, vdelecroix escribió:
Does your remark applies to both the pexpect GAP interface and libgap?
AFAIK this only affects the pexpect interface
Antonio Rojas
May 1, 2021, 2:23:13 PM5/1/21
to sage-devel
Opened #31761 for this
Reply all
Reply to author
Forward
0 new messages