On Jun 3, 5:06 pm, Craig Citro <[email protected]> wrote:
> > I should point out that simply starting from scratch and creating this
> > object uses 1.19GB of virtual memory (primarily because I use an
> > entire permutation generator), so it's not like the memory is small
> > and then gets large (though it does get consistently larger while
> > saving). But I don't understand why the process of saving should
> > never end. Thanks for any ideas.
>
> Can you post some code that generates this (or better yet, a smaller
> example of the same ilk) so that we can all play around?
sage: L=[]
sage: P=Permutations(some number greater than 9, depending on your
computer's memory)
sage: for p in P:
sage: ... L.append(p)
sage: ...
<takes a while>
sage: save(L,'L')
<takes a LOT longer, if indeed it ever finishes, and is NOT POSSIBLE
to Ctrl-C out of for some reason>
But I am now thinking it's my machine. What is the expected behavior
if an object nearly maxes out your memory and you then try to save it
(and if you try to interrupt it when it takes a while)? That is the
situation here.
Also, is there any way to access the size or any other (non-
mathematical) attributes of any unsaved Sage object while the session
is running? I'm thinking of something like the du command but for a
Sage session. Presumably the object must have some existence in RAM,
but on the other hand it doesn't live in a file so I can't just look
for it and then click for information. Maybe that's a naive question.
Sorry if this turns out to be noise.
- kcrisman
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
