Dear Dragan,
What you're describing you want to do is beyond the scope of pytables
itself. Pytables already does all that could be expected of it, namely
releasing the GIL so that other Python threads can execute while a
long-running C-API call is executed. The question of number of CPUs is
A Dijous 02 Març 2006 16:47, vàreu escriure:
> Hello again!
>
> Fisrt of all I am working on single CPU machine. I do
> have a seperate thread for listening to external
> commandas. The idea is that all long jobs should be
> started as seperate threads (e.g. writting data to a
> table) but should n
Hello again!
Fisrt of all I am working on single CPU machine. I do
have a seperate thread for listening to external
commandas. The idea is that all long jobs should be
started as seperate threads (e.g. writting data to a
table) but should not block light jobs for being
executed. In my example a li
A Dijous 02 Març 2006 15:25, dragan savic va escriure:
> Hi everybody!
>
> I am working on using PyTables with multiple threads.
> I am writting an application where some of the
> PyTables related jobs will run for a longer time.
> During that time it would be a good thing that I could
> send some
Hi everybody!
I am working on using PyTables with multiple threads.
I am writting an application where some of the
PyTables related jobs will run for a longer time.
During that time it would be a good thing that I could
send some non-time consuming commands to the
application without waiting for a
Hi Mike,
A Dimecres 01 Març 2006 18:48, Mike Romberg va escriure:
> Hi
>
> We are starting up a new project at the lab I work for and have
> decided that pytables is just the thing to use for data storage.
> However we will need to have multiple processes access the data in a
> read/write manner
