-
Bug
-
Resolution: Fixed
-
Later
-
3.8.2
-
None
-
Security Level: Jimmy
-
None
-
Sprint 3, Sprint 4
steps to reproduce
- run the attached project (version 3.8.3.FL.20160106-Eval)
- test under Firefox 42
- in merge(), call notifyAffectedRange(event);
- click headers to insert columns upon the order below
9103
9131
9119
9160
9150
9170
9105
9110
- in merge() , change to call notifyLoadedRange();, perform the previous step
result
- see attached report
- notifyLoadedRange(); is slower than another approach.
Execution time: measured from clicking the header cell to seeing a rendering complete.
- But the number of cells in this range is smaller (225120) than another (325242). The loaded range doesn't reduce during scrolling, it starts from A1:DE201 to A1:FO201 during testing
- notifyLoadedRange(); have average bigger response size than another.
expected result
- notifyLoadedRange(); is faster than notifyAffectedRange(event);
- The time taken by notifyLoadedRange(); doesn't increase by more and more column insertions.
- relates to
-
ZSS-1176 java.lang.IllegalStateException: Form too large207605>200000
- Closed