I will remove the per default Async logging in 2.1.0 See http://jira.codehaus.org/browse/MRM-1842
On 3 May 2014 03:36, Miguel Almeida <[email protected]> wrote: > I wanted to clarify my last email - > http://logging.apache.org/log4j/2.x/manual/async.html explains the > advantages of async loggers. But it seems to me that there's a huge CPU > load associated with it (which is not documented there). > I haven't used log4j's async logging before - is there some optimisation > missing in archiva, or is such a high load really expected? > > Miguel > > > On Fri, May 2, 2014 at 6:21 PM, Miguel Almeida > <[email protected]>wrote: > >> The provided link doesn't offer much information on the difference between >> the different AsyncLogger.WaitStrategy strategies. >> What are the pros and cons of the different options? >> >> I was already using 1.4-M4 and noticing constant high cpu loads (15% CPU >> usage even on idle periods). >> >> Cheers, >> >> Miguel >> >> >> On Fri, May 2, 2014 at 12:06 PM, Miguel Almeida <[email protected] >> > wrote: >> >>> Original URL provided by Oliver is broken. Link should point to >>> http://archiva.apache.org/docs/2.0.1/adminguide/logging.html >>> >>> >>> On Thu, Apr 10, 2014 at 7:11 PM, Allen Lee <[email protected]> wrote: >>> >>>> Changing the wait strategy to Block in wrapper.conf fixed it for me. >>>> Thanks Olivier! >>>> >>>> On Wed, Apr 9, 2014 at 5:31 PM, Olivier Lamy <[email protected]> wrote: >>>> > Maybe because of the async logging from log4j2 (using disruptor). >>>> > Have a look here: >>>> > http://archiva.apache.org/docs/2.0.2-SNAPSHOT/adminguide/logging.html >>>> > >>>> > HTH >>>> > -- >>>> > Olivier >>>> > >>>> > On 10 April 2014 05:07, Allen Lee <[email protected]> wrote: >>>> >> I upgraded from Archiva 1.3 to Archiva 2.0.1 recently and noticed that >>>> >> archiva's CPU usage is consistently high, around 80-85%. I reniced the >>>> >> process and now it's ranging from 15-85% of CPU, on average around >>>> >> 40-50%. At first I thought it might have been the initial startup >>>> >> costs of rescanning repositories but it has remained this way after >>>> >> several days now. >>>> >> >>>> >> The admin system status page doesn't report anything untoward (no >>>> >> repository scans happening, etc.). Any suggestions on how to fix this, >>>> >> and is this something others have noticed as well? >>>> >> >>>> >> Thanks in advance! >>>> >> >>>> >> -- >>>> >> Allen Lee >>>> >> Center for the Study of Institutional Diversity [http://csid.asu.edu] >>>> >> School of Human Evolution and Social Change [http://shesc.asu.edu] >>>> >> College of Liberal Arts and Sciences >>>> >> Arizona State University | P.O. Box 872402 | Tempe, Arizona 85287-2402 >>>> >> 480.727.0401 | Fax: 480.965.7671 | e-mail: [email protected] >>>> > >>>> > >>>> > >>>> > -- >>>> > Olivier Lamy >>>> > Ecetera: http://ecetera.com.au >>>> > http://twitter.com/olamy | http://linkedin.com/in/olamy >>>> >>>> >>>> >>>> -- >>>> Allen Lee >>>> Center for the Study of Institutional Diversity [http://csid.asu.edu] >>>> School of Human Evolution and Social Change [http://shesc.asu.edu] >>>> College of Liberal Arts and Sciences >>>> Arizona State University | P.O. Box 872402 | Tempe, Arizona 85287-2402 >>>> 480.727.0401 | Fax: 480.965.7671 | e-mail: [email protected] >>>> >>> >>> >> -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy
