Re: Profiling .Net code

2006-10-28 Thread Michael Schall
Thanks guys, I'll try this on Monday and report back. On 10/28/06, Ron Grabowski [EMAIL PROTECTED] wrote: There were issues in the past with NLog not reporting the correct Typeand line number logging statements were called from. I'm pretty sure this has been fixed. IBatisNet ships with other

Re: Profiling .Net code

2006-10-27 Thread Michael Schall
Yes and no... If we turn off logging (log4net 1.2.10), the issue goes away... I would think that logging would be a fairly consistent hit. We are using the RollingFileAppender. I am looking into the BufferedForwardingAppender which would then push to the file. I don't want to lose the log that

Re: Profiling .Net code

2006-10-27 Thread Gilles Bayon
I think Ron can have one for NLogOn 10/27/06, Michael Schall [EMAIL PROTECTED] wrote: Yes and no... If we turn off logging (log4net 1.2.10), the issue goes away... I would think that logging would be a fairly consistent hit. We are using the RollingFileAppender. I am looking into the

RE: Profiling .Net code

2006-10-26 Thread Jeremy Gray
your current perf problem. Jeremy From: Michael Schall [mailto:[EMAIL PROTECTED] Sent: Thursday, October 26, 2006 9:46 AM To: user-cs@ibatis.apache.org Subject: Profiling .Net code We are running into some performance issues in our applications using iBatis. Looking at a log4net

Re: Profiling .Net code

2006-10-26 Thread Ron Grabowski
: Profiling .Net code We are running into some performance issues in our applications using iBatis. Looking at a log4net rolling file, times from start to finish of select statements can vary from 15ms to 400+ms for the same call with a sql trace saying that the sp has 0 duration. I am looking