Re: GUI extreme slowness due to log4net

"Di Furness" <[email protected]>
Newsgroups gmane.comp.windows.dotnet.nunit.user
Message-ID <[email protected]>
Hi

I have tried turning every lognet setting to Off or Error in all the
config files provided with Nunit and still it had no effect.  I have
given up trying to use the UI - running the tests within Visual Studio
works fine though.

 

Cheers...Di Furness  Integration Specialist | rL Solutions | T:
61-8-8201-7611| [email protected] <mailto:[email protected]> 

The contents of this e-mail and any attachments are intended solely for
the use of the named addressee(s) and may contain confidential and/or
privileged information. Any unauthorized use, copying, disclosure, or
distribution of the contents of this e-mail is strictly prohibited by rL
Solutions and may be unlawful. If you are not the intended recipient,
please notify the sender immediately and delete this e-mail. Thank you. 

From: [email protected]
[mailto:[email protected]] On Behalf Of Richard
Matsunaga
Sent: Saturday, 16 February 2008 7:04 AM
To: [email protected]
Subject: Re: [Nunit-users] GUI extreme slowness due to log4net

 

I too am having problems with logging and NUnit. My application uses
NHibernate, which has very verbose logging that results in the unit
tests running 100x (or more) slower than without the log2net logging.

 

Our build server has a slightly older version of NUnit and tests are
practically instantaneous, even with data layer tests that set up and
tear down the database for each test. I'm very afraid of upgrading NUnit
there due to the logging.

 

I don't understand log4net and its configuration very well, but I can't
seem to find a way to stop the NUnit GUI from reporting all the
NHibernate logging.

 

Does anyone have a suggestion?

 

Richard

 

________________________________

From: [email protected]
[mailto:[email protected]] On Behalf Of Di
Furness
Sent: January 30, 2008 5:45 PM
To: Charlie Poole; [email protected]
Subject: Re: [Nunit-users] GUI extreme slowness due to log4net

Hi

These tests ran fine in a previous version of nunit because there was
not the clash of use of log4net.  Is there something else I have to
disable in the config file?

I have tried creating a specific config file and nominating that in the
Project definition screen.  This does not seem to make any
difference...all the debug logging is obviously still occurring.  If I
turn all the debug logging on within Visual Studio it is slow as well
but that would be expected.  I can get the logs not to display (by
turning off the log tab) but that does not seem to disable the logging
(ie to make the tests faster). 

 

The config file I am editing is the default one nominated by nunit and
in the same directory as the assembly being tested.  I get very minimal
output displayed in the GUI.  The run time in the GUI for 6 tests was
224.09 whereas the same 6 tests ran within Visual Studio in 8.34
secs...significantly different.

 

The log4net entry in my config file which I edit after Visual Studio has
created one specifically for the assembly is:

  <log4net>

    <appender name="Console" type="log4net.Appender.ConsoleAppender">

      <layout type="log4net.Layout.PatternLayout">

        <conversionPattern value="%class %level - %message%newline"/>

      </layout>

    </appender>

    <root>

      <level value="ERROR"/>

      <appender-ref ref="Console"/>

    </root>

    <logger name="RadicaLogic.Framework">

      <level value="ERROR"/>

    </logger>

    <logger name="RadicaLogic.Terminology">

      <level value="ERROR"/>

    </logger>

  </log4net>

 

I have also tried simplifying it by removing 

    <logger name="RadicaLogic.Framework">

      <level value="ERROR"/>

    </logger>

    <logger name="RadicaLogic.Terminology">

      <level value="ERROR"/>

    </logger>

 

I still get extremely slow performance in the nunit GUI.

 

Cheers...Di Furness  Integration Specialist | rL Solutions | T:
61-8-8201-7611| [email protected] <mailto:[email protected]> 

The contents of this e-mail and any attachments are intended solely for
the use of the named addressee(s) and may contain confidential and/or
privileged information. Any unauthorized use, copying, disclosure, or
distribution of the contents of this e-mail is strictly prohibited by rL
Solutions and may be unlawful. If you are not the intended recipient,
please notify the sender immediately and delete this e-mail. Thank you. 

From: Charlie Poole [mailto:[email protected]] 
Sent: Thursday, 31 January 2008 4:08 AM
To: Di Furness; [email protected]
Subject: RE: [Nunit-users] GUI extreme slowness due to log4net

 

Hi Di,

 

When you say, "default App.config" are you refering to the one used by
your executable? If so, you need to do the same thing in the config for
your tests.

 

However, it's possible that this may not do the job, since the appender
used by the tests is created programmatically. If you verify that the
test config is correct and the problem is still there, please file a
bug.

 

Charlie

	 

	
________________________________


	From: [email protected]
[mailto:[email protected]] On Behalf Of Di
Furness
	Sent: Tuesday, January 29, 2008 7:34 PM
	To: [email protected]
	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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.