I find that very surprising. I was surprised too. I thought SUMPRODUCT would be faster.
T T. Valko Nov 3, 2007 #21 I find that very surprising. I was surprised too. I thought SUMPRODUCT would be faster.
H Harlan Grove Nov 3, 2007 #22 T. Valko said: I was surprised too. I thought SUMPRODUCT would be faster. Click to expand... .... The SUMPRODUCT on its own is almost certainly faster, but all the stuff in the MAX call takes time to process. Another academic question would be how an array formula like =INDEX(rngA,MAX(IF(rngB<>"",ROW(rngB)))) would compare.
T. Valko said: I was surprised too. I thought SUMPRODUCT would be faster. Click to expand... .... The SUMPRODUCT on its own is almost certainly faster, but all the stuff in the MAX call takes time to process. Another academic question would be how an array formula like =INDEX(rngA,MAX(IF(rngB<>"",ROW(rngB)))) would compare.
T T. Valko Nov 5, 2007 #24 Harlan Grove said: ... The SUMPRODUCT on its own is almost certainly faster, but all the stuff in the MAX call takes time to process. Another academic question would be how an array formula like =INDEX(rngA,MAX(IF(rngB<>"",ROW(rngB)))) would compare. Click to expand... It compares favorably when the start of the range is row 1: http://img502.imageshack.us/img502/5467/calctimes11ng0.jpg But it's slower, as is SUMPRODUCT, when you need to calculate the row offset.
Harlan Grove said: ... The SUMPRODUCT on its own is almost certainly faster, but all the stuff in the MAX call takes time to process. Another academic question would be how an array formula like =INDEX(rngA,MAX(IF(rngB<>"",ROW(rngB)))) would compare. Click to expand... It compares favorably when the start of the range is row 1: http://img502.imageshack.us/img502/5467/calctimes11ng0.jpg But it's slower, as is SUMPRODUCT, when you need to calculate the row offset.