Well, this is what I get with Python 2.1, NumPy 20.0.0, Linux on a 450Mhz PIII [cbarker@waves junk]$ python numtst.py 20.0.0 0.438 0.154 0.148 0.139 So whatever it was may have been fixed (or be a strange platform dependence). Note, you do want to be a bit careful about using time.time, as it measures real time, so if you have another process hogging resources, it will not be a fair measure. You can use time.closck instead, although I'm sure it has its issues as well. This is what I get with clock: [cbarker@waves junk]$ python numtst.py 20.0.0 0.440 0.160 0.140 0.140 There's not much going on on my machine right now, so little difference. -Chris -- Christopher Barker, Ph.D. ChrisHBarker@home.net --- --- --- http://members.home.net/barkerlohmann ---@@ -----@@ -----@@ ------@@@ ------@@@ ------@@@ Oil Spill Modeling ------ @ ------ @ ------ @ Water Resources Engineering ------- --------- -------- Coastal and Fluvial Hydrodynamics -------------------------------------- ------------------------------------------------------------------------