Re: performance problem in multithread environment

2010-12-17 Thread Curt Arnold
On Dec 16, 2010, at 9:02 AM, 刘东 wrote: > tanks for you reply. > I write test program to show my appliaction case. > > package com.iss.cnooc.test.ebank; > import org.slf4j.Logger; > import org.slf4j.LoggerFactory; > public class LoggerTest > { >Logger logger = LoggerFactory.getLogger(LoggerT

RE: Re: RE: Re: performance problem in multithread environment

2010-12-17 Thread Sebastien Tardif
ontention. From: 刘东 [mailto:[email protected]] Sent: Friday, December 17, 2010 1:40 AM To: Log4J Users List Subject: Re: Re: RE: Re: performance problem in multithread environment Hi,I use jprofiler to monitor appliaction,the result shows that,at the same time only on thread is runing,t

Re: Re: RE: Re: performance problem in multithread environment

2010-12-16 Thread 刘东
: http://jakarta.apache.org/log4j/";> I turned asyn BufferSize to 10240,but the test result is no changing. why? 2010-12-17 刘东 发件人: Sebastien Tardif 发送时间: 2010-12-17 02:32:38 收件人: 'Log4J Users List' 抄送: 主题: RE: Re: performance problem in multi

Re: RE: Re: performance problem in multithread environment

2010-12-16 Thread 刘东
://jakarta.apache.org/log4j/";> I turned asyn BufferSize to 10240,but the test result is no changing. why? 2010-12-17 刘东 发件人: Sebastien Tardif 发送时间: 2010-12-17 02:32:38 收件人: 'Log4J Users List' 抄送: 主题: RE: Re: performance problem in multithread environ

Re: RE: Re: performance problem in multithread environment

2010-12-16 Thread 刘东
the test result is no changing. why? 2010-12-17 刘东 发件人: Sebastien Tardif 发送时间: 2010-12-17 02:32:38 收件人: 'Log4J Users List' 抄送: 主题: RE: Re: performance problem in multithread environment File IO is slow, you need to have a asyncappender between your application and file i/o. ---

RE: Re: performance problem in multithread environment

2010-12-16 Thread Sebastien Tardif
File IO is slow, you need to have a asyncappender between your application and file i/o. -Original Message- From: 刘东 [mailto:[email protected]] Sent: Thursday, December 16, 2010 10:02 AM To: Log4J Users List Subject: Re: Re: performance problem in multithread environment tanks for

Re: Re: performance problem in multithread environment

2010-12-16 Thread 刘东
| 46859 2| 96593 4| 196921 16 | 717703 I use fileappender. why? 2010-12-16 刘东 发件人: Curt Arnold 发送时间: 2010-12-16 14:15:03 收件人: Log4J Users List 抄送: 主题: Re: performance problem in

Re: performance problem in multithread environment

2010-12-15 Thread Curt Arnold
On Dec 13, 2010, at 10:54 AM, Jacob Kjome wrote: > You will get better performance by not logging at all, no question. However, > there are tuning possibilities. I see you mention "logger.info()". In > production, I generally only have "warn()" and above for the vast majority of > loggers.

Re: performance problem in multithread environment

2010-12-13 Thread Jacob Kjome
e specifics, especially if you feel you truly are taking these issues into account and are still getting ridiculously bad performance while using Log4j. Jake On Mon, 13 Dec 2010 09:54:04 +0800 wrote: I need your help!!! Please help me ,thanks. 2010-12-13   2010-12-11 01:52:03 Log4J

Re: Re: Re: performance problem in multithread environment

2010-12-12 Thread 刘东
I need your help!!! Please help me ,thanks. 2010-12-13 刘东 发件人: 刘东 发送时间: 2010-12-11 01:52:03 收件人: Log4J Users List 抄送: 主题: Re: Re: performance problem in multithread environment hi, through jprofiler I found that many thread are blocked at logger.info(message).I saw that each

Re: Re: performance problem in multithread environment

2010-12-10 Thread 刘东
without log,application will process 40 orders one second. Is there any mistakes by using log4j?need more config? thanks. 2010-12-11 刘东 发件人: Sebastien Tardif 发送时间: 2010-12-11 01:10:40 收件人: log4j-user 抄送: 主题: Re: performance problem in multithread environment The code show that

Re: performance problem in multithread environment

2010-12-10 Thread Sebastien Tardif
The code show that synchronization is by category. If appendLoopOnAppenders is faster, like if the underline code use asynchronous appender, that should not be a problem. So you should investigate what the thread having the lock is doing. ---