I would really like to see some improvement in the environment 'initial' setup speed after a publish.
Just after a initial deploy the loading of pages can take a very long time,
especially when this publish concerns several larger E-spaces.
It would be nice if the executed actions during a first run can e.g. be done upfront at the end of a publish.
A high latency is considered innoying to end-users, and will be noticed
more when a lot of publishes are done during working hours.
To avoid this one can delay publishes or schedule an evening job.
The scheduling as an evening job would probably result in "slow system"
user notifications every morning after and less control over a publish.
Besides that delaying a publish will lead to a longer project cycle.
It would be very nice if there would be a caching method that would make sure the webservers' cache would be filled with an initial load of the page / execute of the queries involved so the system would be responsive, even directly after a publish.
Currently as a workaround I'm thinking about creating an E-space that
would execute a HTTPGet on all clickable links in an E-space.
I would however need to create a list of all possible links that are to be clicked and besides that need to maintain this while I think the environment is perfectly aware of these links and there is probably a more efficient way to cache both queries and pages.