[sage-devel] Re: The high memory cost of creating many Polyhedron objects

2015-04-30 Thread Dima Pasechnik
On Tuesday, 17 February 2015 14:55:35 UTC, Nathann Cohen wrote: > > Hello everybody, > > I am trying to compute a couple of things on polyhedra, and for that I > need to generate and test a lot of them, each at a time. While I never > store them in any way my code stops after a while because o

[sage-devel] Re: The high memory cost of creating many Polyhedron objects

2015-04-29 Thread Nils Bruin
On Wednesday, April 29, 2015 at 1:11:22 AM UTC-7, jplab wrote: > > Hi, > > I had not noticed that Polyhedron created a Poset, and if so that 'makes >> sense'. I had the same problem with both classes: it makes it very hard to >> create a lot of Polyhedron objects, or many posets (and this, in tur

[sage-devel] Re: The high memory cost of creating many Polyhedron objects

2015-04-29 Thread jplab
One thing could be to see how much of the information of the face lattice is required for some specific methods... Perhaps some of them could be implemented without using the face lattice in certain cases and be just as fast... -- You received this message because you are subscribed to the Goo

[sage-devel] Re: The high memory cost of creating many Polyhedron objects

2015-04-29 Thread jplab
Hi, I had not noticed that Polyhedron created a Poset, and if so that 'makes > sense'. I had the same problem with both classes: it makes it very hard to > create a lot of Polyhedron objects, or many posets (and this, in turns, > makes it hard to write a routine that enumerates posets up to iso

[sage-devel] Re: The high memory cost of creating many Polyhedron objects

2015-04-29 Thread Nathann Cohen
Hello, Have a look at the thread Memory leak in Polyhedron object > > . > > Would that be the problem for you? In this case, the problem is the ticket > #14356. > I had no

[sage-devel] Re: The high memory cost of creating many Polyhedron objects

2015-04-29 Thread jplab
Hi Nathann, Have a look at the thread Memory leak in Polyhedron object . Would that be the problem for you? In this case, the problem is the ticket #14356. Best, JP Le m