Mailing-List: contact users-help@archiva.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@archiva.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Sender: Brett Porter <brett@porterclan.net>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Re: Limit memory usage for Archiva
From: Brett Porter <brett@apache.org>
In-Reply-To: <11525652.1101338347028549.JavaMail.root@mail.deventm-group.org>
Date: Wed, 30 May 2012 14:08:42 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D2A804C-4627-433F-872C-88282BB7D291@apache.org>
References: <11525652.1101338347028549.JavaMail.root@mail.deventm-group.org>
To: users@archiva.apache.org


On 30/05/2012, at 1:03 PM, Erwin Mueller wrote:

> Thank you for your answers,
>=20
> So trimming down of Archiva is not an option? Is all indexing done in =
memory? I would think that the index is saved on disk and loaded on =
demand?

The indexing is done incrementally, but a full scan or frequent uploads =
does create a queue that will consume memory for a period of time, as do =
individual requests. If you have low traffic, you can probably get away =
with less and reduce the heap size, but the lower you go there's a =
chance that garbage collection will slow down normal operation. You can =
look at the system status page to see if your memory use is reaching the =
limit. You can still trim it down using the techniques I've described as =
well.=20

- Brett

--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter