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 not block light jobs for being > executed. In my example a light job is executed after > the heavy one. I just want to improve the > interactivity so I don't wait for something that could > be executed immediately without blocking.
And sending both long jobs and lighter ones to different threads does not help? I'm not an expert on threading, but my guess is that if you send a job A to thread 1 that takes, say, 3 minutes to get done and 1 minute after that, you send a job B to thread 2 that takes 1 seconds, I think that the job B should get done shortly after 1 minute an 1 second. Again, I'm not an expert on threading, so perhaps you can get some feedback about your problem in the general python list. Cheers, -- >0,0< Francesc Altet http://www.carabos.com/ V V Cárabos Coop. V. Enjoy Data "-" ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users
