On Wednesday 01 October 2003 04:13, Brion Vibber wrote:
Anybody wanna look into optimizing OutputPage::replaceInternalLinks()? It's a known troublemaker; it's got a bit loop that could probably be much much more efficiently done.
Why would not pages be rendered when saved and stored on disk as HTML, as they are typically saved once and viewed many times? As I understood, disk space is not a problem, but processor time is.