FYI: Simon's patch doesn't make any difference for the amount of
memory used for
sage: while p<2^20:
....: p=next_prime(p)
....: g=FindGroupOrder(p,11)
....:
In both cases about 2046MB more were used after the loop :(. Simon:
Run
init_mem=get_memory_usage()
before you do anything, run the computation and then once you are done
run
get_memory_usage()-init_mem
and compare the different to before the patch. I assume Alex's script
he attached to the ticket does something similar.
It might be a good idea to create some constant at the very end of
all.py that sets the initial amount of memory used so it is trivially
invokable because once you have hit a leak it is too late anyway :(
Not that the patch will fix some other issues, but the picture seems
to be more complex. I am sure we will get to the bottom of it :).
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
