well day 3 was pretty productive if you ask me! I completed a great Hand's on tutorial for both c# 3.0 and Silverlight 1.1. I'm actually really looking forward to trying to build some 1.1 apps now! One of the talks I went to inparticular was excellent called Top Ten ASP.net Scaling Tips by Stephen Forte.
Stephen is a big player in large scalable systems, having experience with NFL super bowl sunday sites and the NASDAQ - it's a pretty impressive resume. Below are some of the key parts:
What is Scalability - A system is scale if we can add more workload to a system without increasing the cost of the system per unit of workload.
Characteristics of a Scalable System
-
It can ramp up to a large number of users quickly
-
It can do so without increasing the cost per use (CPT)
-
It can do so while keeping the cost per user as low as possible
Top 5 Key ways to increase performance via code
-
Eliminate view state - Reduce data sent to and from client
-
Eliminate session state - use as few session variables
-
Output caching - use caching
-
Fragmented Output caching - put anything that can't be cached normally into a user control, then cache that.
-
SQL Server Query notification - check SQL Performance
Images
Every file on your server that you access is counted as a 'round trip', so if you have 20 images it does a request 20 times. So if you have a site thats got a 100ms overhead it'll be 20x100ms. By using a single image with
Session State
Try to store alot of none-secruity information in hidden fields on your web page. Try to remove session view state by using tools like strangeluke
-
R = (payload/bandwidth) + Round Trip Time+ (AppTurns(RTT)/Concurrent Requests) + Cs(Server Side Compute time) +Cc (Client Compute time)
-
App Turns = Http Requests
-
RTT Round Trip TimeTry PayLoad/Bandwidth first then Compute Time
Datasets
Try using stored procedure algrorithms that return items in ranked order. So first 100 items, then next 100 etc. Be sure to do this on the sql server
LINQ
Stay away from LINQ in large sites, stick to using stored procedures. use linq on quick sites.
Stored procedures
Really good performance, very secure. Ideal database should have all its I-O's threw stored procedures, and only those stored procedures are allowed to run select/update statements.
Be the first to rate this post
- Currently 0/5 Stars.
- 1
- 2
- 3
- 4
- 5