Yep. It is definitely faster: $ time ./bin/test <testing> real 8m18.517s user 4m6.898s sys 0m4.019s $ time python t.py (with ipcluster local -n 2) <testing> real 5m31.959s user 0m0.602s sys 0m0.290s $ time python t.py (with ipcluster local -n 4) <testing> real 4m30.470s user 0m0.494s sys 0m0.227s $ time python t.py (with ipcluster local -n 8) <testing> real 6m0.355s user 0m0.654s sys 0m0.229s
I only have 2 cores, but I think it benefits from having more threads anyway. I think I can see what you mean with the 8 threads though. I will need to find a process manager for the Mac that lets you view what different threads are doing and on what cores. htop is Linux only. Aaron Meurer On Jul 16, 2009, at 5:00 PM, Ondrej Certik wrote: > > On Thu, Jul 16, 2009 at 4:31 PM, Aaron S. Meurer<[email protected]> > wrote: >> >> Never mind. I was referring to the mec = client.MultiEngineClient() >> command, but it seems that you need to have ipcluster running for >> that >> to work too. > > Yes, the ipcluster starts ipengines on your machine, or remote > cluster/server. (you can also start ipengines manually). Then you run > your clients, in the ipython session, or just t.py in the sympy > parallel branch, which just uses ipython to communicate with > ipcluster. > > It's very cool, you can play with it in the shell. > > Ondrej > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sympy?hl=en -~----------~----~----~----~------~----~------~--~---
