close

Вход

Забыли?

вход по аккаунту

?

Getting the Best Performance Out of DotNetNuke

код для вставкиСкачать
Mitchel Sellers, CEO
IowaComputerGurus Inc.
п‚Ў
п‚Ў
п‚Ў
п‚Ў
п‚Ў
Active in the DotNetNuke eco system for about 3 years
Author of Professional DotNetNuke Module Programming
Provider of support to many clients with varying
DotNetNuke installation configurations
Documents Module Team lead
CEO of IowaComputerGurus Inc.
п‚Ў
What impacts performance





п‚Ў
Infrastructure (Hosting Environment)
Configuration (DNN Settings)
Modules/Skin Objects
Skin Design
Traffic
Getting the best performance
 Tuning for the hosting environment
 Default configuration changes
п‚Ў
п‚Ў
Next Steps/More Drastic Measures
Questions?
п‚Ў
п‚Ў
Why?
Types of hosting
 Shared
 Cloud (Distributed)
 Virtual Server (VPS)
 Dedicated Server
п‚Ў
Location of SQL Server
п‚Ў
Shared
 Low cost
 Low available RAM/CPU
 Moderate Disk IO
п‚Ў
Cloud
 Moderate cost
 Unstable RAM allotment/Moderate CPU
 Very fast Disk IO
п‚Ў
VPS
 Moderate cost
 Limited RAM (1-2 Gb)/Moderate CPU
 Moderate-Fast Disk IO
п‚Ў
Dedicated
 High Cost
 High amount of RAM/CPU
 Moderate-Fast Disk IO
п‚Ў
SQL Server Location
 Adds layer of complication to the assessment of
other hosting aspects
п‚Ў
п‚Ў
п‚Ў
п‚Ў
Is locally installed SQL bad?
Best configuration?
Most secure configuration?
Ways to combat issues?
п‚Ў
п‚Ў
Baseline DNN Configuration
Host Settings
 Performance settings
 Timer mode
 Schedule configuration
п‚Ў
Future Concerns
 Event Log
 Site Log
п‚Ў
п‚Ў
п‚Ў
Recurring errors
Improper development practices
Slow rendering/Lack of Cache
 SolPart menu
п‚Ў
п‚Ў
Invalid HTML
Number of installed modules
п‚Ў
CSS Vs. Tables
 Size
 Rendering speed
 Content placement
п‚Ў
п‚Ў
п‚Ў
Image/CSS size
Skin Objects used
Panes used
п‚Ў
Low Traffic
 ASP.NET Worker Process Shutdowns
в–Є Re-configure IIS
в–Є Use service such as MyWebKeepAlive.com
 Cloud or other hosting not allocating enough
resources
п‚Ў
High Traffic
 Database contention
 Lack of Caching/Compression
п‚Ў
п‚Ў
Start with core settings changes
Baseline performance testing
 DotNetNuke 4.9.0 website
 SolPart Menu
 Default Configuration/Shared Hosting
 Average page load time 3.2 seconds
п‚Ў
Performance Settings
 Module Caching Method
▪ Cloud/VPS – Disk
▪ Shared/Dedicated – Memory
 Performance Setting
в–Є Heavy Caching
 Compression
в–Є GZip (Unless using 3rd party)
п‚Ў
Other Settings
 Disable Users Online (Yes)
 Scheduler Mode (Timer)
 Enable Event Log Buffer (Yes)
 Auto-Sync File System (No)
п‚Ў
Scheduler
 Search Indexer
в–Є Frequency should be lengthened
п‚Ў
Authentication Providers
 By default all are enabled
 Average default load time 3-6 seconds for login
п‚Ў
Disable ALL unused providers at “Host
Settings” level
 Doing this with default providers (OpenId and
LiveId) resulted in login page load of under 1
second
п‚Ў
Must be done at the host level, cannot be
controlled by template
п‚Ў
п‚Ў
Almost instant change
Unauthenticated requests
 Reduced load time to low 2 second mark, a 33%
improvement
 Improvement can be greater depending on size of
content
п‚Ў
п‚Ў
Evaluation of installed modules, remove unnecessary ones
Consider skin change from SolPart to other
menu provider.
 Have seen performance improvements of 30-50%
when using CSS NavMenu
п‚Ў
Consider third-party caching system
 Have seen consistent improvements with Snapsis
Page Blaster
п‚Ў
DotNetNuke 4.9.4 site
 2000 users
 300 blog posts
 3-4 k forum posts
 ~600-1000 visitors a day
 Shared hosting 1.9~2.4 seconds avg load
 Dedicated hosting 0.7-1.2 seconds avg load
п‚Ў
п‚Ў
My Blog – http://www.mitchelsellers.com
Snapsis – http://www.snapsis.com
Документ
Категория
Без категории
Просмотров
4
Размер файла
96 Кб
Теги
1/--страниц
Пожаловаться на содержимое документа