[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Was: Index... Now: Vectorize, huh?

"Pavel A. Romashkin" <pavel.romashkin@noaa.gov> writes:

> Craig and Med,
> I appreciate it! This is exactly what I needed. My problem is the lack
> of matrix operations knowledge. Craig's generic solution is exactly what
> I expected to see from Craig :-)

You're welcome.

> By the way. We all are big on vectorizing things in IDL. But look at this:
> IDL> a = test(2000)
>        1.4968959
> IDL> a = test(2000, /v)
>        3.2976190
> where TEST is below. I don't even mention that /VEC causes extremely
> high memory usage and gets totally out of hand on my system if S > 5000
> or so.

Yes, you can go too far overboard with vectorization.  Part of the
problem is that you coded your vectorized path inefficiently.  However
I think that when your matrices start to get huge, then the benefits
of vectorization can actually degrade, especially when you need to
artificially promote vectors into matrices as you are doing.

I've always said that if you can vectorize the inner loop of your
operation then you are usually fine.  Pavel, you actually did that in
your *non*-vectorized case. :-)

A new version of TEST improves things slightly, but doesn't tip the
scales. w/ your version I get 1.6 and 3.8 s.  With my version I get
1.5 and 2.7 s.


pro test, s, vec=vec
start = systime(1)
x = findgen(s)
if keyword_set(vec) then begin
  a = rebin(x,s,s)^2
  a = sqrt(transpose(a) + a)
endif else begin
  a = fltarr(s, s)
  for i = 0, s-1 do begin
    a[0, i] = sqrt(x^2 + i^2.)
print, systime(1) - start

Craig B. Markwardt, Ph.D.         EMAIL:    craigmnet@cow.physics.wisc.edu
Astrophysics, IDL, Finance, Derivatives | Remove "net" for better response