snip

I would venture to say that the vast majority of threads in these groups are
primarily relating to projects of *not* gigantic proportions, so that the
actual capacity and/or capability of XL never really becomes a matter of
significant importance ... EXCEPT among the responders themselves, for their
own enlightenment and/or edification.

snip

I would bet that your assessment is correct!

My biggest "pet peeve":

=LOOKUP(9.99999999999999E+307,................)

Who has time to count all those 9's and make sure you're using just the
right amount?

=LOOKUP(MAX(A:A)+1,...............)

Or, if you know the max value WILL NEVER be 1000

=LOOKUP(1000,...............)

Biff

"Ragdyer" wrote in message
...
In the past couple of months I've been made aware of numerous fallacies
concerning the "old wives tales" of the efficiency of various procedures
and
functions, whether they pertain to arrays OR volatility.

I would venture to say that the vast majority of threads in these groups
are
primarily relating to projects of *not* gigantic proportions, so that the
actual capacity and/or capability of XL never really becomes a matter of
significant importance ... EXCEPT among the responders themselves, for
their
own enlightenment and/or edification.

Therefore, what you've just mentioned doesn't really surprise me at all.

My own personal involvement in XL efficiency has been limited to a
solitary
function mix of replacing Vlookup with Index & Match, where a 40,000 to
50,000 row dB WB was vastly improved by the revision.

Everything else pertaining to speed and efficiency I've picked up here
(whether true or false), within these groups.

Therefore I would tend to believe that the main goal in putting forward
suggested solutions would (should) be clarity and simplicity and
understandability (is that a word?<g), and let the efficiency syndrome
take
a back seat, except when either expressly mentioned, or insinuated, as
part
of the actual request.
--
Regards,

RD

---------------------------------------------------------------------------
Please keep all correspondence within the NewsGroup, so all may benefit !
---------------------------------------------------------------------------

"Bob Phillips" wrote in message
...
"Ragdyer" wrote in message
...

It's usually wiser to try not to use array formulas where possible,
since
they tend to use more of XLs computing capability.

All of the formulae that use array ranges, whether that be in array
formulae, or as arrays in a non-array formula, use a lot of resources.

I did some timings for my SP page (which I still need to post), and I
found
that SP using a double-unary operator was the quickest SP type, and was
quicker than a SUM(IF((cond1)*(cond2), data), but other SP types (*,
N,1*,+0) were as slow or slower. And surprisingl;y, the array type
SUM(IF(cond1,IF(cond2,data)) was the fastest of all.