Re: Performance hit with Debug = True

If you are looking to enhance performance, try running the profiler and see
where all of your time is being spent.
Also look at the performance section in the MSDN Library
One thing to watch for is doing a lot of boxing/unboxing.
Your best bet might be to upgrade to .Net 2005 and use collections instead
of things like arraylist etc.

Kismet
"Wade" <wwegner23NOEMAILhotmail.com> wrote in message
news:u8Y3U9igFHA.2896@xxxxxxxxxxxxxxxxxxxxxxx
> Hi Bob,
>
> Thanks for the comments. Yes, this has actually come up because our
> clients have been complaining about the performance of our applications,
> and I've been trying to compile (no pun intended) a list of possible
> performance enhancements we can make.
>
> Wade
>
> "Bob Grommes" <bob@xxxxxxxxxxxxxx> wrote in message
> news:OycRjvegFHA.3124@xxxxxxxxxxxxxxxxxxxxxxx
>> Wade,
>>
>> I seldom do release builds for the reasons your "pro-debug" group cite,
>> plus all of my code is released internally to my customers (not released
>> into the wider world where there might be concerns about reverse
>> engineering, which of course is much easier with a debug release) and
>> because my debug builds run plenty fast enough.
>>
>> Does the app run fast enough to satisfy you and its users? Then don't
>> worry about the debug overhead unless there is some lengthy processing
>> which runs appreciably faster in release mode such that it significantly
>> impacts user productivity and bottom line. (Sometimes users may be
>> content, but faster processing still translates into saved dollars,
>> whether users recognize this or not).
>>
>> I am speaking here mainly of console and winforms apps (and to a lesser
>> extent, windows services). I have only completed ASP.NET apps with small
>> numbers of users and haven't looked into whether debug builds would hurt
>> scalability. Quite possibly, this would be a bigger factor in ASP.NET
>> applications, particularly public sites with large numbers of users.
>> Same would go for web services.
>>
>> --Bob
>>
>> "Wade" <wwegner23NOEMAILhotmail.com> wrote in message
>> news:etg24vagFHA.2700@xxxxxxxxxxxxxxxxxxxxxxx
>>> Hi all,
>>>
>>> (Sorry for the cross-post -- just noticed this group.)
>>>
>>> We have a debate going on here in the office. There's one group that
>>> would
>>> prefer to have our LIVE environment with debugging turned on, because
>>> it's
>>> convenient when there's an error, and another (myself included) that
>>> would
>>> prefer not to have debugging turned on. So, I ask you all: is there
>>> really
>>> a significant overhead in having this turned on?
>>>
>>> And by turned on, I mean that all PDB files are copied out into the \bin
>>> folder, and the compilation tag (in the web.config) has the debug
>>> property
>>> set to true.
>>>
>>> Thanks for your help and opinions!
>>>
>>> Wade
>>
>>
>
>


.

Relevant Pages

  • Re: Performance hit with Debug = True
    ... Wade ... > because my debug builds run plenty fast enough. ... I have only completed ASP.NET apps with small ... > applications, particularly public sites with large numbers of users. ...
    (microsoft.public.dotnet.framework.performance)
  • Re: Performance hit with Debug = True
    ... I seldom do release builds for the reasons your "pro-debug" group cite, ... of course is much easier with a debug release) and because my debug builds ... I am speaking here mainly of console and winforms apps (and to a lesser ... extent, windows services). ...
    (microsoft.public.dotnet.framework.performance)
  • Re: Else Without If
    ... "tmort" wrote in message ... that is a LOT of code and I wouldn't expect anyone to wade through that lot on here. ... It would almost certainly make it easier to follow and debug. ... Just my 2p worth. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Running smartdevice applications (CF) on the desktop from VS.N
    ... "David Jones" wrote in message ... >> Debugging CF apps on the desktop with CF 1.0 is not supported (with CF ... >> Even if you could debug them, remember that your code will be running ... >> against the desktop framework where some things are different (including ...
    (microsoft.public.pocketpc.developer)
  • Im in asp.net 1.1 hell....re debugging and breakpoints.
    ... I have googled til my fingers hurt and am ... Both machines will also debug a C# asp.net 1.1 app with no problems. ... no breakpoints get hit in the Page_load of the main.aspx ... asp.net apps ...
    (microsoft.public.dotnet.framework.aspnet)
Loading