关于DNN的性能增强

关于DNN的性能增强,转自http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/486/Default.aspx
作者:Charles Nurse (DNN核心团队成员)
Many people have commented that the dotnetnuke.com site is a little slower with the recent upgrade to 4.3.1 (especially for Login).

If your site has a lot of users, you are probably getting the same "poor" performance.  (Note - the problem is not confined to 4.3.1 - it will also be a problem with 3.3.1, as it is due to one of the new User features).

However, there is a simple solution, and here it is.

1. Log in as admin or host
2. Go to the "User Accounts" module (on the Admin menu).
3. Select the "User Settings" module action
4. Click Update to save the Settings.

Savvy users will have by now figured out the problem - The User Settings, which are implemented as Module Settings in the Database do not exist (are null).  Loading the User Settings page loads the default values and clicking "Update" persists them to the database.

Normally, when custom Module Settings are not "set" this does not affect performance but in this case there is a very expensive query that is run when retrieving the default settings.  This query will run every time a setting is needed, because, the GetSetting uses a fallback approach:

a) - try fetching the settings from the Cache
b) - try fetching the settings from the Database
c) - load the default settings (which calls the expensive query GetUserCountByPortal)
d) - get the setting from the collection of settings

On this site, when logging in, 3 different settings are needed, so the query is made 3 times - at a cost of about 800ms each (due to 300,000 users), hence the performance issues.

Now that I have carried out the procedure above (1-4) on this site, the default settings have been persisted to the Database, and the caching mechanism can work -  Login is much faster.

A fix will be added to the next version, so that default values are automaticaly saved to the database on upgrade (or first access).

posted on   公众号73只蚂蚁  阅读(353)  评论(2编辑  收藏  举报

编辑推荐:
· 为什么 .NET8线程池 容易引发线程饥饿
· golang自带的死锁检测并非银弹
· 如何做好软件架构师
· 记录一次线上服务OOM排查
· Linux实时系统Xenomai宕机问题的深度定位过程
阅读排行:
· 2025年广告第一单,试试这款永久免费的开源BI工具
· o3 发布了,摔碎了码农的饭碗
· 为什么 .NET8线程池 容易引发线程饥饿
· 用 2025 年的工具,秒杀了 2022 年的题目。
· .NET 响应式编程 System.Reactive 系列文章(一):基础概念

导航

< 2008年7月 >
29 30 1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31 1 2
3 4 5 6 7 8 9
点击右上角即可分享
微信分享提示