Re: GUI extreme slowness due to log4net

Hi Di,

I'm not sure if this is related but the words "bad performance" and "NUnit GUI" strike a chord for me, so it's potentially worth a shot! Not too long ago we ran into very slow NUnit GUI performance after we upgraded our code base to VS2005. Running in the NUnit console was more or less unaffected. (I'm not sure about the NUnit integration with VS2005 since I have never yet tried it. (We have licenses for TestDriven.NET, but I personally like to see those green lights in the NUnit GUI :-)

Anyway, back to the point; we did some research into the performance issue that we encountered and found that our particular performance issue is caused by VS2005 itself.

One of the developers that did this particular piece of research pointed us to these links.

General Debugger Performance Info:
http://blogs.msdn.com/jimgries/pages/visual-studio-debugger-faq.aspx
 
MDA Performance Problem:
http://blogs.msdn.com/jmstall/archive/2006/01/17/pinvoke_100x_slower.aspx
http://blogs.msdn.com/tlai/archive/2006/06/15/How-to-Disable-a-Specific-MDA.aspx

After reading and absorbing the above, we decided that internally the best use for us was to use the environment variable approach. "To disable MDAs via an environment variable, define an environment variable named COMPLUS_MDA and set it equal to 0." Note that this also requires a reboot.

After doing this the performance of the NUnit GUI was back to the performance levels we had experienced in previous versions under VS2003 and also now consistent between the NUnit GUI and console.

Hopefully this information helps, but if not I wish you all the best in trying to resolve your performance issue.

Regards,
Wayne Hartell.


  ----- Original Message ----- 
  From: Di Furness 
  To: [email protected] 
  Sent: Wednesday, January 30, 2008 2:04 PM
  Subject: [Nunit-users] GUI extreme slowness due to log4net


  Hi

  When I run the tests within visual studio, they run very quickly but within the GUI they are EXTREMELY slow.  This seems to be due to the fact that all DEBUG messages are still being generated and  captured not filtered even if my default App.config does have them set to INFO.  Can you suggest how to fix this in the GUI?

   

  Thanks.Di



------------------------------------------------------------------------------


  -------------------------------------------------------------------------
  This SF.net email is sponsored by: Microsoft
  Defy all challenges. Microsoft(R) Visual Studio 2008.
  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/


------------------------------------------------------------------------------


  _______________________________________________
  Nunit-users mailing list
  [email protected]
  https://lists.sourceforge.net/lists/listinfo/nunit-users

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
Nunit-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nunit-users