Thanks. I misunderstood the setup. I saw the Log4jBackgroundProcess and hoped this would separate the overhead of the file i/o from the PL/SQL thread. We're running on an 8-way system, and PL/SQL generally seems to sit on one CPU. Our debug logging is adding about 10% to the processing time. In theory, if I can push the logging overhead to a second thread, I should see about a 10% performance increase.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, September 28, 2006 10:39 AM To: Thompson, John Cc: [email protected] Subject: Re: Log4plsql Performance John, Unfortunly, we have never compare all log4plsql performance with util_file. But in V3 for writing into file, log4plsql use util_file package. Intuitively it must be very similare Guillaume Selon "Thompson, John" > Guillaume, > > I just read your article on OTN about log4plsql. Just curious about how the > performance of log4plsql compares to writing log information via the > util_file package. We're using util_file for debug messages, and running > into a surprising amount of overhead. > > Thanks, > > JT > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Log4plsql-all-info mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net
