Very slow SUMIF performance when using "Row Range Notation"

[grahamorrell]

Description

I have an Excel workbook (minimal example attached) which has some SUMIF( ) formulae that use "Row Range Notation", for example :

=SUMIF(2:2, B11, 4:4)

These perform very poorly in Excelize despite there only being 25 columns in the worksheet. To calculate the sum of 8 of these SUMIF( ) statements takes over 3 seconds.

If I change the SUMIFs to also specify the columns, for example :

=SUMIF(B2:Y2, B11, B4:Y4)

Performance is dramatically improved, taking just 8 milliseconds to calculate the sum of 8 of them.

Steps to reproduce the issue:

1. Call CalcCellValue on a SUMIF( ) using Row Range Notation

Describe the results you received:

Describe the results you expected:

Performance should be almost identical in both cases because the sheet only has 25 columns.

Output of go version:

N/A

Excelize version or commit ID:

excelize-wasm 0.0.7

Windows
SUMIF Performance.xlsx

[paolobarbolini]

I'm trying to fix this in #2111. Not all tests pass yet but I'd expect the final implementation to fix your issue without having to manually restrict the range.

[xuri]

I fixed incorrect formula calculation result for cell "Test SUMIF"!D16 in workbook "SUMIF Performance.xlsx". Issue caused by shared formula parsed error. This patch will be released on next version, and excelize-wasm NPM package will be updated soon.