Hi Jonathon,
 
Thanks a lot for your reply! It was quite disappointing news, though. What
I did to investigate it further was to play around with the Visual Studio
2010 Beta 2 installation I have on my hard drive. This is what I found out
(copied from a comment I wrote on the issue tracker page):
 
"I ran into this problem recently, and it was quite annoying. However, I
did some testing now with Visual Studio 2010, beta 2.
 
I recompiled my own projects with .NET 4.0, no change (still the bad
performance).
 
I recompiled DynamicProxy with .NET 4.0 as well, and *now* the bug is
actually _gone_!!! Which is way cool, great news for us, since DynamicProxy
plays a key role in this project.
 
So, no need to wait for .NET 6.0; this will very likely work with the final
version of .NET 4.0 as well."
 
Best regards,
Per Lundberg

________________________________

From: [email protected] on behalf of Jonathon Rossi
Sent: Wed 3/17/2010 12:13 PM
To: [email protected]
Subject: Re: Problems with DynamicProxy: massive performance degradation
when running inside VS2008 debugger


Hi,

Many people have reported this issue over the years, however the defect is
out of our control. Please see this task for more information:
http://support.castleproject.org/projects/DYNPROXY/issues/view/DYNPROXY-ISS
UE-72


On Wed, Mar 17, 2010 at 7:54 PM, Lundberg, Per <[email protected]>
wrote:


        Hi guys,
         
        We are developing an application using DynamicProxy, and it has
worked fine until now. A certain operation (which involves creating 69
proxy objects) takes an extensive period of time when running the
application.
         
        I did an analysis of the problem and my conclusion is this:
         
        - When running inside Visual Studio (debugger attached), it takes
around 20 seconds for the operation to complete.
        - When running without debugger (Ctrl-F5), it takes around 2
seconds, with the exact same build of the code.
        - When changing the object instantiation to use the "regular"
non-proxy class, the operation takes around 6 seconds (with debugger
attached).
         
        So... there you have it. Something with the way my
code/DynamicProxy works is making it slow down quite a lot when running
with debugger. Any ideas?
         
        I tried enabling "Just My Code" but it didn't make any difference.
         
        The problem is that when running in e.g. the ANTS Profiler (which I
have a license for), I'm getting the "medium-fast" behavior so I cannot
really track the problem that way either... :-)
         
        (Initially, there was a problem with the way I was doing the proxy
generation. I instantiated a new ProxyGenerator each time I needed a proxy
object, which is obviously the wrong way to do it. That showed a
performance hit in ANTS, but it now looks OK when I look at the profiling
results there. So, DP "should" really not be the problem here, but
still...)
         
        --
        Best regards,
        Per Lundberg

        

        -- 
        You received this message because you are subscribed to the Google
Groups "Castle Project Users" group.
        To post to this group, send email to
[email protected].
        To unsubscribe from this group, send email to
[email protected]
<mailto:castle-project-users%[email protected]> .
        For more options, visit this group at
http://groups.google.com/group/castle-project-users?hl=en.
        




-- 
Jono


-- 
You received this message because you are subscribed to the Google Groups
"Castle Project Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Castle Project Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/castle-project-users?hl=en.

Reply via email to