On May 24, 2010, at 4:33 PM, jtg wrote:
> solver time > ------------------------------------------- > pysparse 0m19.014s > trilinos w 1 proc 1m33.709s > trilinos w 4 proc 0m49.786s > > It would appear that the parallelization is indeed > working, but that it just doesn't have much to > work with. In each case I verified that the > FIPY_SOLVERS env variable was set correctly, > that I was using FiPy-2.1, and that the expected > number of processors was engaged. I did *not* > explicitly specify a particular solver. This is generally consistent with what I'm seeing my MacBook (2.26 GHz Intel Core 2 Duo, 4 GB RAM) running examples/phase/anisotropy.py (*with* viewers) for 10 steps solver 100x100 500x500 1000x1000 pysparse 5.75 65.8 287 Trilinos w 1 proc 12.6 176 844 Trilinos w 2 proc 13.7 134 710 This is not at all the optimal machine to test this on, but it's a data point. We will get some better benchmarks and try to develop some guidance as soon as possible.
