DBMetadataCacheResults
DB Metadata Cache results
(From John Baker)
Comparing Visual Web projects that have a page with a Table component bound to a (remote) MySQL database rowset vs. a page with a Table component bound to an ObjectArrayDataProvider {OADP). *
Binding to an ObjectArrayDataProvider performance is closely equivalent to binding to a DdlUtils local metadata file. Using a DdlUtils exported metadata file, there will a small increase in performance due to delay in reading and parsing a persisted file.
Bind to Data (refreshing the Table Layout dialog)
ObjectArrayDataProvider - ~ less than .5 second
CachedRowSetDataProvider (rowset connections) - ~ 1.5 seconds
Depends on the number of columns in the database table. More tables then accessing could take longer
Open project (1 page with 3 Table components bound)
Project A: ObjectArrayDataProvider only - ~ 7 seconds
Project B: CachedRowSetDataProvider (rowset connections) - 9 seconds
Totals
OADP CRSDP
Binding < .5 sec. 1.5 sec
Open prj 7 secs 9 secs.
Binding CRSDP to a Table component is more than 1 second slower than OADP project Opening a CRSDP project is about 2 secs slower OADP OADP
More Results
Starting IDE (no projects opened)
OADP 22 seconds
CRSDP ~ 27 seconds
Starting IDE (projects opened, no pages opened)
OADP 7 seconds
CRSDP ~ 15
