On Mar 7, 9:47 pm, William Stein <wst...@gmail.com> wrote: > With a function as *trivial* as your f above, the overhead of > @parallel will kill your benchmark. As I explained, for *every* > single call, an entire copy of Sage is forked off. This is no problem > if evaluating f takes at least a second (say), but it kind of > pointless for something like the above. > > -- William
I have created a simple time-exhaustive function to compute some million elements FFT. Each call was taking approximately 5 secs. However I couldn't get speed-ups with @parallel on my dual core 2.5 Ghz cpu laptop. Could you provide an example showing the @parallel use with an easy-observable example? I am going to give a demonstration on Wednesday and I would like to be able to demonstrate this feature as well. Thanks again William. -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
