try yourself. Take the welcome app from 2.8.2.
If /welcome/default/index takes more than 50ms to be served, then it's the server/web2py config.
My laptop of 4 years ago with Ubuntu 12.10 loads the page in 22ms with the rocket webserver.
First round of fetching static assets with an empty cache takes it to 360ms.
EDIT: pythonanywhere, a hosting provider that surely doesn't shine on performances (free account), assures 320ms (tested from home, Italy). 64ms are for DNS lookup, 228ms to transfer the data. This leaves roughly 30ms to generate the webpage.
EDIT2: harsh summary:
- if your app on your local machine on the internal webserver renders any page taking more than 500ms, touching the config is not where I'd go first to assure good response times on your production server
- even if 500ms are achieved on your local machine and your prod server takes 2000ms with the exact same setup, then your prod needs to go to wasteland