[
https://issues.apache.org/jira/browse/TAP5-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657088#action_12657088
]
Howard M. Lewis Ship commented on TAP5-417:
-------------------------------------------
I'm working through a number of issues; there is no way we can compete
head-to-head on extremely large pages because of the in-memory DOM. There may
be an option to keep more of the DOM virtual until render time, but that may
handicap attempts to do more involved post-processing of markup than what
Tapestry does ... for example, it would be nice to be able to post-process the
DOM to highlight search resutls and if too much of the content is virtual that
won't be possible.
Anyway, what I'm working on now is reducing the number of rendering steps by
skipping render phases when they are no-ops.
> Tapestry 5.0 Performance Improvements
> -------------------------------------
>
> Key: TAP5-417
> URL: https://issues.apache.org/jira/browse/TAP5-417
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.0.18
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> Make it work. Make it right. Now we're making it fast.
> T5 is as fast or faster than JSP for trivial pages; for pages that render a
> lot (i.e., lots of loops) T5 is not keeping up. It may not (it does so much
> more) but we need to narrow the gap.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
