This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The caching only works for anonymous users. At launch there is a danger that many people will create accounts, not intending to edit now, but rather in the abstract future. If we get a lot of people doing this and viewing many pages, the site could fall over. We should have a banner on the sign-up page that explains that we may need to disable new account sign-ups due to high load, and if that happens folks should come back in a few days to sign up. Then, we should be prepared to flip the switch to disable new logins if we get to the danger point during the launch.
Ideas: * Bump the session time down low to automatically sign out users for the first few days. Or a way to to clear all logged in users manually if we get to a danger zone. * Have a way to turn off new signups. * A banner asking people not to stay signed in.
I've added an option at the bottom of Settings.php that can be uncommented to turn off account creation. Disabling login isn't terribly easy. Also, it's fairly difficult to purge sessions, since they are stored in memcache with a key of the ID. I'll continue to look into it, though.
This didn't turn out to be necessary.