Complete scan of all the content in the data structure, resulting in slow performance

Undetected bottlenecks due to inefficient code.

Exception Management

Round trips to servers and expensive calls

Expensive compared to returning enumeration or Boolean values

Increased inefficiency

Adds to performance overhead and can conceal information unnecessarily

Resource Management

Can result in creating many instances of the resources along with its connection overhead

Increase in overhead cost affects the response time of the application; Not releasing (or delaying the release of) shared resources, such as connections, leads to resource drain on the server and limits scalability

Retrieving large amounts of data from the resource increases the time taken to service the request, as well as network latency

This should be avoided, especially on low bandwidth access, because it affects response time

Increase in time spent on the server also affects response time as concurrent users increase

Leads to resource shortages and increased memory consumption; both of these affect scalability

Large numbers of clients can cause resource starvation and overload the server.

In-process and local state stored on the Web server limits the ability of the Web application to run in a Web farm. Large amounts of state maintained in memory also create memory pressure on the server

Increased server resource utilization, and increased time for state storage and retrieval

Inappropriate timeout values result in sessions consuming and holding server resources for longer than necessary.