I run http://www.colr.org http://www.colr.org, which is powered by web.py. It has survived several digg / lifehacker / other high-traffic incidents. If you ar

I run http://www.colr.org http://www.colr.org, which is powered by web.py. It has survived several digg / lifehacker / other high-traffic incidents. If you are running web.py as a fcgi process, you'll handle a digg effect just fine. If not, you'll peg the server and your site will be largely unavailable. Happily, switching web.py from fcgi to non-fcgi mode or back again is a single-line change :)