On Sat, Sep 29, 2018 at 9:46 AM Simon King <simon.k...@uni-jena.de> wrote: > > Hi Dima, > > On 2018-09-29, Simon King <simon.k...@uni-jena.de> wrote: > > Anyway, using set_gap_memory_pool_size(2*get_gap_memory_pool_size()) > > till everything works sounds like a reasonable way out. > > Too bad: When the error occurs and I adjust the pool size then > afterwards the previously defined objects in gap are gone. > > So, is it possible to adjust the pool size dynamically *without* the > need to repeat all computations in Gap from scratch?
no, this is by design of GAP. There is no real harm in doing set_gap_memory_pool_size(10*get_gap_memory_pool_size()) as you are limiting maximal memory, not the initial memory allocated for GAP - at worst your Sage crashes... If coset enumeration is the bottleneck, you should not use GAP's built-in one, by use the one in ACE GAP package, it is much faster and efficient with memory etc. HTH Dima > > Best regards, > Simon > > -- > You received this message because you are subscribed to the Google Groups > "sage-support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-support+unsubscr...@googlegroups.com. > To post to this group, send email to sage-support@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-support. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
