Jonathan, thank you for this thoughtful analysis. With a really simple function, I get the output
0 1066.03125 0 1066.03125 0 1066.1640625 0 1066.1640625 0 1066.29296875 0 1066.29296875 0 1066.29296875 0 1066.29296875 0 1066.421875 0 1066.421875 0 1066.421875 0 1066.421875 0 1066.421875 0 1066.421875 0 1066.421875 0 1066.5546875 0 1066.5546875 0 1066.5546875 .... and constant afterwards. I do not know whether the initial rise is a problem but I suspect not. I get the same behavior on the small (4G) machine, only with different numbers of course. The output of overcommit_memory is zero, so that's not it. I am quite willing to share my code with you and others who think they can help at a similar level of commitment, but would prefer not to publish the code where anyone else could read it. Please suggest a private channel if you are interested - I could open a dedicated gmail address and post it here, unless you have a better idea. Denis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
