Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.co.uk;
  h=Received:X-YMail-OSG:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:thread-index:Content-Language;
  b=TsdIs+9HeiEoLP/CFEMAXI3sbKpbkoeAN5ZJUi31Fo7PIFmu5OPO2d7utpA8E45DeTaX9O9rwnz+OSiid3pZwgXpp1F818hFtylY/WH0GlG5gON7zMAE3ctC5yei36u9JZ1lsAYT3DvbRRgQ0VWk9Le7tZfzau+7Jqs44Njb2xU=
  ;
From: "sbarriba" <sbarriba@yahoo.co.uk>
To: <users@jackrabbit.apache.org>
Subject: Memory usage issues of importml/exportsysview
Date: Fri, 5 Oct 2007 08:40:29 +0100
Message-ID: <035a01c80723$020a2c10$061e8430$@co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_035B_01C8072B.63CE9410"
thread-index: AcgHIwAYgWdQ3iagQUS5qRSrkIzeyA==
Content-Language: en-gb

------=_NextPart_000_035B_01C8072B.63CE9410
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all,

During a recent thread Hot Backup Tools were discussed - see
http://www.mail-archive.com/users@jackrabbit.apache.org/msg04255.html.

 
As an outcome of that we're doing 2 things:

1)      "Low-level" backup

o   Backing up the database

o   Backing up the repository file system

2)      "High-level" backup

o   Running exportsysview on each workspace 

 
When migrating between environments or restoring backups solution 2) is very
useful although the XML files are getting very large where the content has
lots of binaries etc. The main issue is that the memory requirements of
"importxml" increase linearly with the size of the XML file. I presume this
is due to either a) the memory required to parse the file, and/or b) the
memory required to hold the transient state of the import.

 
We're now needing to use a 1GB heap size for some imports and obviously this
will hit a crunch point.

 
Any suggestions on how to resolve this memory issue? For example, could the
"importxml" not use a SAX event model to avoid parsing the XML into a
complete DOM etc (note I don't know the internals of importxml as it
stands).

 
All suggestions welcome.

Regards,

Shaun

 
------=_NextPart_000_035B_01C8072B.63CE9410--