Best Practices for Accelerating Problem Resolution

in .NET Applications and Web Services

Garbage Collection

(GC)

Application and

Framework settings

(e.g. max number of

threads in thread pool

is insufficient)

Inefficient use of

Remoting (e.g. too much

data transferred in each

Remoting call)

Interoperability

End-user mistakes

The Black Box records performance

counters related to .NET GC. These

counters indicate the status of GC at

any point in time. Fully synchronized with

all other recorded data (e.g. assembly

invocations, database calls, process

start, and more), a developer can easily

identify GC-related problems.

The Black Box records all necessary

performance counters, messages written

to the Event Log, as well as application

and framework settings (.NET config file

accesses, IIS configuration and browser

settings). Integrated into the Black Box

log, this data allows the support engineer

to pinpoint non-optimized settings that

cause application slow downs.

The Black Box records all Remoting calls

(both on the client and server sides) and

presents their performance in the application

performance dialog, thus allowing a

developer to pinpoint the slow performing

calls. When required, the AppSight user

can drill down to analyze execution of

Remoting calls at the code level.

The Black Box records the interactions

of the application with home grown and

3rd party components, thus allowing

the AppSight user to easily identify

performance bottlenecks that are caused

by external .NET and legacy components.

The Black Box records all end-user

actions and allows a support engineer to

play them back as a movie or text, thus

pinpointing end-user errors and easily

understanding the end-user experience.

2006 Identify Software, Ltd.

13

END-USER ERRORS