Quantcast
Channel: ADO.NET, Entity Framework, LINQ to SQL, NHibernate
Viewing all articles
Browse latest Browse all 1698

Scalability Problem

$
0
0

Good day, I am currently faced with improving the Scalability of an Asp.net 4.0 C# web system.  The Business logic is all written Using Linq to Sql calling Stored Procs with parameters.Database is SQL 2008 R2.  Our main issue is that increased traffic on the site Causes the whole system to become slow and unresponsive, compared to when only a few users are connected.  I used this toolhttps://www.loadtestingtool.com/ to do Initial load load testing (20 users) and this confirmed my fears that the system does not handle higherloads efficiently. Currenly this sends the processor through the roof for minutes on end.

Here are my initial Guesses at bottlenecks the System. 

  • Object Mapping (Appcontext) adds extra processing to every request and is not needed
  • Transaction scope used could potentially Lock other Other User requests
  • Linq to Sql driver might not be the right approach for high Volume Web applications  (why does query run quick in SSMS not in code)
  • Slow / long running SQL Queries cause performance issue (for instance Exports)
  • Old / irrelevant data needs to be Archived to improve speed
  • Database Design
  • Server Configuration / Architecture
  • Old version of SQL server (2008 R2)

Can anyone shed some light on this situation ? How does one go about eliminating the above . For instance do you start with the database or application Code?


Viewing all articles
Browse latest Browse all 1698

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>