![]() |
![]() |
#1 (permalink) |
Banned from being Banned
Location: Donkey
|
ASP.net and Page/Application Tracing
I have an asp.net application that references a DLL I've created. I wanted to test the speed of the application as a whole so I added an argument to each class' constructor that takes in the TraceContext arg.
Now, within my code in the DLL, I have Traces usually around each major function. If I disable Tracing via the web.config, will leaving those Trace.Write methods in the code slow things down, or does it just disregard them? I figure this is a good way to test the performance of my apps as I can leave the trace code inside the DLL and just enable tracing whenever I want to see overall page performance, but I'm unsure of the effects of leaving Trace code within my DLLs.
__________________
I love lamp. |
![]() |
![]() |
#2 (permalink) |
Crazy
Location: Belgium
|
They have absolutely no effects on performance whatsoever!
Leaving the trace statements inside the code while switching tracing of or on in the web.config is the whole purpose of application tracing. When trace enabled="false", trace statements will be completely disregarded, the same as comments.
__________________
Amerika by Franz Kafka “As Karl Rossman, a poor boy of sixteen who had been packed off to America by his parents because a servant girl had seduced him and got herself a child by him, stood on the liner slowly entering the harbour of New York, a sudden burst of sunshine seemed to illumine the Statue of Liberty, so that he saw it in a new light, although he had sighted it long before. The arm with the sword rose up as if newly stretched aloft, and round the figure blew the free winds of heaven.” |
![]() |
Tags |
aspnet, page or application, tracing |
|
|