On 6/26/12 11:19 PM, Aquil H. Abdullah wrote:
> Hello All,
>
> In my newbist state, I called createIndex on two columns in one of my
> tables:
>
> import tables
> table_desc = {'timestamp':tables.Time32Col(),
> 'symbol':tables.StringCol(8), 'observation':tables.Float32Col()}
> h5f = tables.openFi
Hello Francesc,
Thank you for your response! I guess I need to read the User's Guide cover to
cover.
--
Aquil H. Abdullah
On Wednesday, June 27, 2012 at 4:44 AM, Francesc Alted wrote:
> On 6/26/12 11:19 PM, Aquil H. Abdullah wrote:
> > Hello All,
> >
> > In my newbist state, I called
Sorry about that, I uploaded the code, but since it requires
many dependencies, I was not expecting you to run it. That being said, I
would say the expected number of rows per table is 100,000 and I am
currently working on an intel xeon with 4 processors and 8 threads.
I also found that pytables h
Update:
It actually seems that I am bottlenecking in my performance before I even
get to writing data. It seems that my current search procedure is very
computationally ineffcient. I have pasted the active portion of my code,
and I have also attached the copy of my dataWrapper. I have narrowed the
Hello PyTables Users,
I am asking this quick question because my application is currently
horribly bottlenecking on these methods, all of which are called once
before each Table.append(rows). The table writing on the other hand is
much, much faster than the searching for the table.
Any general di
