Hi Lucas,

I haven't had a look at database traffic of core language specific pages yet, since we don't use it for our clients. It looks like there is lazy loading of a number of settings one by one and portal languages are not cached in API and redone numerous times. These issues can only be fixed in the API, my script is optimizing scripts being called to improve response time, but this would not reduce the number of calls. There are a number of areas, where API needs to be optimized, e.g. user accounts module is retrieving all UserIDs for a page and subsequently loads individually UserInfo, Membership, UserProfile and UsersOnline status per record, i.e. for 20 records it queries the database up to 81 times. Another sample is new DAM, which supports paging - on the client site, while the server always retrieves the full set of files per folder.

Obviously, there is still room for performance improvements in DNN.