Hi Anthony,
I tried your suggestion and it has not solved the problem. It could be that
it makes the problem go away in the test code because it changes the timing
of the processes. I'll see if I can modify the test code to reproduce the
hang even with reloading the tables module.
Regards,
Owen
On 10 October 2012 22:00, Anthony Scopatz <scop...@gmail.com> wrote:
> So Owen,
>
> I am still not sure what the underlying problem is, but I altered your
> parallel function to forciably reload pytables each time it is called.
> This seemed to work perfectly on my larger system but not at all on my
> smaller one. If there is a way that you can isolate pytables and not
> import it globally at all, it might work even better. Below is the code
> snippet. I hope this helps.
>
> Be Well
> Anthony
>
> def run_simulation_single((paramspace_pt, params)):
> import sys
> rmkeys = [key for key in sys.modules if key.startswith('tables')]
> for key in rmkeys:
> del sys.modules[key]
> import traceback
> import tables
> try:
> filename = params['results_file']
>
>
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Pytables-users mailing list
Pytables-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pytables-users
