incubator-adffaces-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arjuna Wijeyekoon (JIRA)" <adffaces-iss...@incubator.apache.org>
Subject [jira] Created: (ADFFACES-272) Read-Only Table Optimization
Date Wed, 01 Nov 2006 00:49:20 GMT
Read-Only Table Optimization
----------------------------

                 Key: ADFFACES-272
                 URL: http://issues.apache.org/jira/browse/ADFFACES-272
             Project: MyFaces ADF-Faces
          Issue Type: Improvement
            Reporter: Arjuna Wijeyekoon
            Priority: Minor


For an entirely read-only table that also does not contain a per-row button or link, we can
significantly optimize postback to avoid per-row iteration altogether.

UIXCollection knows all about the types of its stamp children - it does this when it walks
the children looking to save/restore each child's internal state
while stamping each row.
So if it finds that there are no EditableValueHolders or ActionSources or any other component
that has internal state, it can optimize postback by 
entirely skipping the decode/validate/update phases on its children.

When I originally profiled the read-only table, I got the following aproximate time distribution
:
decode: ~10%
validate: ~10%
update: ~10%
encode: ~50%

So I think it will be a significant performance improvement for a user browsing (and paging)
a read-only table.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message