Uploaded image for project: 'ZK Spreadsheet'
  1. ZK Spreadsheet
  2. ZSS-1181

notify a loaded range is slower than notify an affected range

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Later Later
    • 3.8.3
    • 3.8.2
    • None
    • Security Level: Jimmy
    • None
    • Sprint 3, Sprint 4

      steps to reproduce

      1. run the attached project (version 3.8.3.FL.20160106-Eval)
      2. test under Firefox 42
      3. in merge(), call notifyAffectedRange(event);
      4. click headers to insert columns upon the order below
        9103
        9131
        9119
        9160
        9150
        9170
        9105
        9110
      5. 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.

        1. 1181.zip
          601 kB
        2. cellCountNotifyChange.png
          cellCountNotifyChange.png
          37 kB
        3. clickHeader.png
          clickHeader.png
          50 kB
        4. comparison.png
          comparison.png
          34 kB
        5. executionTimeComparison.png
          executionTimeComparison.png
          25 kB
        6. responseSizeComparison.png
          responseSizeComparison.png
          20 kB
        7. zss1181TestReport.xlsx
          38 kB

            henrichen henrichen
            hawk hawk
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: