Comments on: Empty NHibernate logs and poor performance http://jagregory.com/writings/empty-nhibernate-logs-and-poor-performance/ Monkeying with the code Tue, 29 Jun 2010 13:30:16 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Lucas Goodwin http://jagregory.com/writings/empty-nhibernate-logs-and-poor-performance/comment-page-1/#comment-11611 Lucas Goodwin Thu, 02 Oct 2008 00:14:54 +0000 http://blog.jagregory.com/?p=105#comment-11611 In addition, the same exception could be thrown during WARN and DEBUG modes... Not being overly familiar with the source of these projects I couldn't say one way or the other, but the DEBUG and WARN configs may not actually make a difference in the scenario you described... In addition, the same exception could be thrown during WARN and DEBUG modes… Not being overly familiar with the source of these projects I couldn’t say one way or the other, but the DEBUG and WARN configs may not actually make a difference in the scenario you described…

]]> By: chrissie1 http://jagregory.com/writings/empty-nhibernate-logs-and-poor-performance/comment-page-1/#comment-11097 chrissie1 Sat, 20 Sep 2008 17:36:23 +0000 http://blog.jagregory.com/?p=105#comment-11097 Log4net (what nhibernate uses) is a non guarenteed service so they do some exception handling and then throw away the exeption. But I think the reason why it slows down is that it takes more time to determine that you can't write then it takes to write to a file. Just a guess though. Like it takes more time to determine a site is not available. it probably tries several times to write to it and then gives up. Interesting. (sorry if i don't make sense ;-)) Log4net (what nhibernate uses) is a non guarenteed service so they do some exception handling and then throw away the exeption. But I think the reason why it slows down is that it takes more time to determine that you can’t write then it takes to write to a file. Just a guess though. Like it takes more time to determine a site is not available. it probably tries several times to write to it and then gives up. Interesting. (sorry if i don’t make sense ;-) )

]]> By: James Gregory http://jagregory.com/writings/empty-nhibernate-logs-and-poor-performance/comment-page-1/#comment-10737 James Gregory Fri, 12 Sep 2008 21:37:29 +0000 http://blog.jagregory.com/?p=105#comment-10737 Damn you and your logic. Without looking at the log4net and NHibernate source, anything I conclude will be purely speculative; however, something must require those permissions and that something must be the root of my performance issues. Curiosity is trying to get me to dig into the source, but down this road madness lies. Damn you and your logic.

Without looking at the log4net and NHibernate source, anything I conclude will be purely speculative; however, something must require those permissions and that something must be the root of my performance issues.

Curiosity is trying to get me to dig into the source, but down this road madness lies.

]]> By: Paul Batum http://jagregory.com/writings/empty-nhibernate-logs-and-poor-performance/comment-page-1/#comment-10731 Paul Batum Fri, 12 Sep 2008 19:41:12 +0000 http://blog.jagregory.com/?p=105#comment-10731 If your theory is correct, why did the problem persist when you changed the log level to WARN? If your theory is correct, why did the problem persist when you changed the log level to WARN?

]]>