Hi! Currently we made some progress in fixing Sage's memory leaks that came from overly-eager permanent caching.
However, as it turned out in trac ticket #12313, some code related with symmetric functions, specifically code introduced in #13762, heavily relies on having permanent caches. In particular, one gets a very dramatic speed regression, as soon as tiny little parents such as "Partitions of the integer 1" can be garbage collected (which apparently has not been the case prior to #12313). Allow me to draw your attention to #13991, where we try to amend it. In particular, note Nils' concluding remarks in comment:10. Perhaps the "combinat tribe" can give us some hints? Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
