Difference between revisions of "Calc/Proposal DataPilot byIBM"
(→Background) |
|||
Line 1: | Line 1: | ||
− | {| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: | + | {| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 50%" |
|- align="left" | |- align="left" | ||
| colspan="2" bgcolor="#cccccc" | '''Specification Status''' | | colspan="2" bgcolor="#cccccc" | '''Specification Status''' | ||
|- | |- | ||
− | | width="150" | '''Author''' || [[User:wangxum|Wang Xu Ming]] | + | | width="150" | '''Author''' || width="150" |[[User:wangxum|Wang Xu Ming]] |
|- | |- | ||
− | | width="150" | '''Last Change''' || See wiki history | + | | width="150" | '''Last Change''' || width ="150"|See wiki history |
|- | |- | ||
|} | |} | ||
− | |||
− | |||
== Background== | == Background== | ||
− | + | DataPilot is a critical function to Spreadsheet users. | |
− | + | In IBM Lotus Symphony 1.2 and 1.3 release, our Spreadsheet team developed several new features for DataPilot base on OpenOffice 1.1 code base and merged DataPilot related code in OpenOffice 2.4. | |
− | + | ||
− | + | ||
+ | During the development, test team found that there is serious performance problem when user create or update a DataPilot table. | ||
== Problem Description == | == Problem Description == | ||
− | '''Allocate a lot of abundant data''' | + | |
+ | '''Low performance when update a datapilot table''' | ||
+ | |||
+ | Test team tested several operations to a sample DataPilot table which have 5000 rows data source. | ||
+ | |||
+ | Below is the test result to OpenOffice 3.0.0: | ||
+ | |||
+ | Test environment: Hardware: IBM T30 CPU: 2.4 GHz Memory:1.0 GB Operation System: Window XP SP2 | ||
+ | {| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 50%" | ||
+ | |- | ||
+ | | width="150" bgcolor="#dddddd" | '''Reference Document'''|| width="150" bgcolor="dddddd"| | ||
+ | |- | ||
+ | | ||available | ||
+ | |- | ||
+ | | || n/a | ||
+ | |- | ||
+ | |} | ||
+ | '''Crash''' | ||
+ | |||
+ | Insert two field into row area ( Each field have about 1000 members ),it causes freezing and crash. | ||
+ | |||
+ | |||
+ | == Analyzing result == | ||
+ | '''Allocate a lot of abundant data''' | ||
For a simple datapilot table: | For a simple datapilot table: | ||
[[Image:simple dptable.jpg]] | [[Image:simple dptable.jpg]] |
Revision as of 09:57, 23 June 2009
Specification Status | |
Author | Wang Xu Ming |
Last Change | See wiki history |
Background
DataPilot is a critical function to Spreadsheet users. In IBM Lotus Symphony 1.2 and 1.3 release, our Spreadsheet team developed several new features for DataPilot base on OpenOffice 1.1 code base and merged DataPilot related code in OpenOffice 2.4.
During the development, test team found that there is serious performance problem when user create or update a DataPilot table.
Problem Description
Low performance when update a datapilot table
Test team tested several operations to a sample DataPilot table which have 5000 rows data source.
Below is the test result to OpenOffice 3.0.0:
Test environment: Hardware: IBM T30 CPU: 2.4 GHz Memory:1.0 GB Operation System: Window XP SP2
Reference Document | |
available | |
n/a |
Crash
Insert two field into row area ( Each field have about 1000 members ),it causes freezing and crash.
Analyzing result
Allocate a lot of abundant data For a simple datapilot table: Member A1 in L1 field will create a array for all members {B1,B2,B3}. But only B1 is visible and valid. Allocate too much memories Every member's data is stored in a big structure. Set too many times of border styles for output area Some borders are set twice or more.
Solution
Data Source buffer A document stored a source buffer array. Every table have a buffer id. The datapilot table can use the same id if they have same data source. In the buffer, the members of a field can be identified by an id( the sorted index ). Then in the output table's algorithm the ScDPItemData structure is replaced by an id. Only allocate visible member Enhance the algorithm of setting border style