Return-Path: Delivered-To: apmail-xml-xmlbeans-dev-archive@www.apache.org Received: (qmail 5289 invoked from network); 10 Dec 2003 12:25:41 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 10 Dec 2003 12:25:41 -0000 Received: (qmail 39309 invoked by uid 500); 10 Dec 2003 12:25:39 -0000 Delivered-To: apmail-xml-xmlbeans-dev-archive@xml.apache.org Received: (qmail 39277 invoked by uid 500); 10 Dec 2003 12:25:39 -0000 Mailing-List: contact xmlbeans-dev-help@xml.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: xmlbeans-dev@xml.apache.org Delivered-To: mailing list xmlbeans-dev@xml.apache.org Received: (qmail 39262 invoked from network); 10 Dec 2003 12:25:37 -0000 To: xmlbeans-dev@xml.apache.org Subject: high volume processing MIME-Version: 1.0 X-Mailer: Lotus Notes Build V65_M2_06122003NP June 12, 2003 From: "Matthias Kubik" Message-ID: Date: Wed, 10 Dec 2003 13:25:35 +0100 X-MIMETrack: Serialize by Router on D12ML015/12/M/IBM(Release 5.0.9a |January 7, 2002) at 10/12/2003 13:25:35, Serialize complete at 10/12/2003 13:25:35 Content-Type: multipart/alternative; boundary="=_alternative 00443789C1256DF8_=" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N --=_alternative 00443789C1256DF8_= Content-Type: text/plain; charset="US-ASCII" Hi all, I'm new to this list as I could not find any thing that would indicate memory problems in the list archive. Now, here's what happened: I was trying the easypo sample as described o the web site. After some script fixing (Linux) I finally got the sample to work. As I have a requirement to process xml files that are 100MB+ in size, I had some expectations...that were not fulfilled. It seems that even a 30MB file would run into an out-of-memory error. I know I could temporarily fix that with giving the JVM more memory. But this is not a solution. To me this looks like the whole DOM tree (if any) and the Object hierarchy is kept in memory. I'd love to see something more "intelligent" there. My question now is, will that be addressed in V2 or is it even a design goal? (didn't find anything in the project mgt, tho). Thanks - matthias --=_alternative 00443789C1256DF8_= Content-Type: text/html; charset="US-ASCII"
Hi all,
I'm new  to this list as I could not find any thing that would indicate memory problems in the list archive.
Now, here's what happened:

I was trying the easypo sample as described o the web site. After some script fixing (Linux) I finally got the sample to work.
As I have a requirement to process xml files that are 100MB+ in size, I had some expectations...that were not fulfilled.
It seems that even a 30MB file would run into an out-of-memory error.  I know I could temporarily fix that with giving the
JVM more memory. But this is not a solution. To me this looks like the whole DOM tree (if any) and the Object hierarchy is
kept in memory. I'd love to see something more "intelligent" there.
My question now is, will that be addressed in V2 or is it even a design goal? (didn't find anything in the project mgt, tho).

Thanks
 - matthias --=_alternative 00443789C1256DF8_=--