What a truly awful response Sebastian! If I were new to DNN, reading this from a DNN Team member would make me leave DNN and never look back. I'm sure there are still hundreds of things that can be done to the DNN core to improve performance without negatively impacting security, stability, or features. That's the nature of our business.

From what I've read, DNN 6.1.2. is supposed to be faster than previous versions. That's the key point of the client resource management stuff. I would guess Jeroen has run into some kind of an "edge case" that someone in DNN Corp should be looking into as you can bet he's not the only one seeing it.

Jeroen, I have seen cases where setting up module caching caused a significant performance hit for some modules. I would definitely look at removing the cache settings and then rerunning your tests and then add the cache settings back for each module type to try and find the culprit.

I started to reply to this post earlier, but I didn't think a forum reply would give this topic the proper attention it deserved.  Our Engineering & Product Management teams take performance very seriously.  We are constantly looking into ways to improve performance and making sure that new features don't cause performance issues.  However, sometimes we have to make gradual improvements in order to eventually have a significant improvement.  I just posted a new blog entry that provides some background on how we measured the performance improvements in 6.1 and how we still have room for improvement.