B
Brett Robichaud
Does anyone know what kind of overhead is caused by enabling tracing in an
ASP.NET 1.1 app?
On my production servers I'd like to leave it enabled so I can view
trace.axd to get a feel for the activity and problems on my site, I'd leave
pageOutput="false". But I'm wondering what kind of extra load my servers
experience due to this. Any ideas?
I'm also curious how bumping up the requestLimit increases the overhead?
I'd like to use a value of 250 or more.
I haven't found any documentation on the overhead associated with tracing.
-Brett-
ASP.NET 1.1 app?
On my production servers I'd like to leave it enabled so I can view
trace.axd to get a feel for the activity and problems on my site, I'd leave
pageOutput="false". But I'm wondering what kind of extra load my servers
experience due to this. Any ideas?
I'm also curious how bumping up the requestLimit increases the overhead?
I'd like to use a value of 250 or more.
I haven't found any documentation on the overhead associated with tracing.
-Brett-