Re: [Pytables-users] Best way to store sequences of arbitrary objects containing arrays

2008-05-21 Thread Anand Patil
OK, that shouldn't be a problem. Thanks for the help! Anand On May 21, 2008, at 9:56 AM, Ivan Vilata i Balaguer wrote: > Anand Patil (el 2008-05-20 a les 22:54:10 +0100) va dir:: > >> On Tue, May 20, 2008 at 9:37 AM, Ivan Vilata i Balaguer <[EMAIL PROTECTED] >> > >> wrote: >> >>> Then, if you h

Re: [Pytables-users] Best way to store sequences of arbitrary objects containing arrays

2008-05-21 Thread Ivan Vilata i Balaguer
Anand Patil (el 2008-05-20 a les 22:54:10 +0100) va dir:: > On Tue, May 20, 2008 at 9:37 AM, Ivan Vilata i Balaguer <[EMAIL PROTECTED]> > wrote: > > > Then, if you have more than 4096 > > nodes, you should be careful not to place them all in the same group to > > avoid performance problems with

Re: [Pytables-users] Best way to store sequences of arbitrary objects containing arrays

2008-05-20 Thread Anand Patil
On Tue, May 20, 2008 at 9:37 AM, Ivan Vilata i Balaguer <[EMAIL PROTECTED]> wrote: > Then, if you have more than 4096 > nodes, you should be careful not to place them all in the same group to > avoid performance problems with the object tree. > Do you mean 4096 leaf nodes, or 4096 nodes in gener

Re: [Pytables-users] Best way to store sequences of arbitrary objects containing arrays

2008-05-20 Thread Ivan Vilata i Balaguer
Anand Patil (el 2008-05-19 a les 17:48:24 +0100) va dir:: > I'd like to store a long sequence of python objects with pytables. The > only things I know about the objects are: > > - Their memory footprint is dominated by a big numpy array, and > - The attribute name of the big array for each obj

[Pytables-users] Best way to store sequences of arbitrary objects containing arrays

2008-05-19 Thread Anand Patil
Hi all, I'd like to store a long sequence of python objects with pytables. The only things I know about the objects are: - Their memory footprint is dominated by a big numpy array, and - The attribute name of the big array for each object is the same; it's x1.big_array, x2.big_array, etc. I