Construction of pages is probably the largest expense for any request, as it involves considerable work to identify what components to instantiate, what bindings to create, and what template tokens to be converted into what ComponentPageElements.
It should be possible to devise a "page template" that is a list of commands for constructing a page. The current PageLoaderProcessor would generate that list of commands. Creating a page instance would be a matter of executing the commands. This would decrease the amount of time needed to generate the 2nd (and later) instances of a page, and would increase the likelyhood that common page elements for literal text could be re-used across page instances.
Making page instance creation less expensive would allow Tapestry to more aggressively cull unused page instances (i.e., shorten the active window) while not sacrificing the ability to handle a request surge.