On Tue, Dec 1, 2009 at 11:48 AM, Faisal Moledina
wrote:
> Eike Welk wrote:
>> Just in case you don't know it, maybe Pytables is the right solution
>> for you. It is a disk storage library specially for scientific
>> applications:
>> http://www.pytables.org/moin
>
> Wow, that looks pretty good. I w
Thanks everyone for your responses!
Alan Gauld wrote:
> You may need to be realistic in your expectations.
> A database is writing to disk which will be slower than working in memory.
> And a 3GB file takes a while to read/traverse, even with indexes. It depends
> a lot on exactly what you are d
Faisal Moledina wrote:
Hey everyone,
I have a general issue that I'd like to discuss. I'm using Python to
run a numerical simulation where at each time step, I run a number of
operations and store the results before moving to the next timestep.
What do you do with the results after the simulat
Hello Faisal!
Just in case you don't know it, maybe Pytables is the right solution
for you. It is a disk storage library specially for scientific
applications:
http://www.pytables.org/moin
The makers claim, that it is fast. It has on the fly data compression
which allegedly makes the library f
"Faisal Moledina" wrote
.
At first, I used a list to store a bunch of class instances, each of
which contained a bunch of data calculated at each time step. This
resulted in whopping memory usage (2.75 GB RAM, 3.75 GB VM).
So then I decided instead to use SQLite to store that information at
eac
Hey everyone,
I have a general issue that I'd like to discuss. I'm using Python to
run a numerical simulation where at each time step, I run a number of
operations and store the results before moving to the next timestep.
At first, I used a list to store a bunch of class instances, each of
which c
