The problem with performance is, that the only relevant number is the speed delivered to the user - and there are a number of factors in the game. Some general speed is derived from the DNN framework and the developers are always keen to provide pest performance, though there is a tradeoff if you want to deliver on the fly individual up2date content. Other factors are machine hardware, connection speed, server configuration (and number of other sites on the same server) as well as modules installed on top of the framework. 

There are a number of general guidelines to follow to improve performance of your site: 

• remove all modules and providers you don't need - this reduces load time and memory footprint
• frequently clean up the database  - truncate transaction log, clear old entries from eventlog, sitelog, schedulehistory and search tables
• enable compression (gzip w/o whitespace compression) and heavy caching in Host Settings
• enable module output caching in module settings where appropriate (for all non-personalized content, which is not updated every few minutes)
• if you are on your own server, optimize app pool recycle; if you are on a shared hosting server, use keepalive.

Johan,

I optimize app recycle only to be executed once per night (e.g. 03:00) and when free resources are under a  specific limit

I disable recycle after inactivity